From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: Multi-arching FLOAT_INFO
Date: Mon, 04 Feb 2002 06:43:00 -0000 [thread overview]
Message-ID: <200202041442.OAA29219@cam-mail2.cambridge.arm.com> (raw)
So it turns out that multi-arching FLOAT_INFO may not be completely
trivial either. Only two ports really make use of this: ARM and i386.
The ARM code is straight-forward, but the code on the i386 is largely
disabled. Indeed, the largest problem is i386b-nat.c which contains a
large chunk of code that is surrounded in "#ifdef FLOAT_INFO". This file
seems to only be used on BSD4.4 systems (FreeBSD, NetBSD and OpenBSD all
seem to use their own nat files -- I'm not sure what BSDi uses).
Since adding FLOAT_INFO to gdbarch will mean that it is now
unconditionally defined the question is - how to handle this chunk of
code. I've no idea (and no way of testing) whether it will even compile
cleanly.
Does anyone even use a system that relies on this file now?
Suggestions welcome.
R.
next reply other threads:[~2002-02-04 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 6:43 Richard Earnshaw [this message]
2002-02-04 8:33 ` Andrew Cagney
2002-02-05 2:34 ` Richard Earnshaw
2002-02-05 7:41 ` Andrew Cagney
2002-02-05 7:57 ` Richard Earnshaw
2002-02-05 8:52 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202041442.OAA29219@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox