From: Ian Lance Taylor <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org, email@example.com
Subject: Re: COFF/PE gas regression: bug
Date: Tue, 06 Apr 1999 08:11:00 -0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Date: Tue, 06 Apr 1999 08:51:02 -0600
From: Donn Terry <email@example.com>
Interesting... I suspect that that explains why the current
gas is the way it is; whether that's right or not I'm not
sure yet. (Clearly, according to the documentation it's
wrong.) I'd like to see the results from a System V i386 COFF
system so we can determine if it's the documentation or
the Motorola code that's wrong.
The SVR3 implementations are pretty much all the same, since the came
from a common code base. I'd be very surprised if they differed.
COFF documentation was always completely inadequate. Don't be
surprised if you see other problems like this.
Moreover, I was moved to check the O'Reilly book on COFF. It says
that C_MOS, C_MOU and C_MOE symbols are N_ABS. Here is the table from
the book (table 8-1, p. 100):
C_EXT N_ABS, N_UNDEF, N_SCNUM
C_LABEL N_UNDEF, N_SCNUM
According to this book, N_DEBUG is for ``a special symbolic debugging
symbol (an assembler symbolic directive)'' and N_ABS is for ``an
absolute value.'' It expands on that by saying that N_DEBUG ``in
general means that the value has no meaning.''
(I suspect we'll need some sort of conditional to resolve this
one, but we'll see.)
Why does it matter? My understanding is that Microsoft doesn't use
that sort of debugging information, so what program actually cares?
next prev parent reply other threads:[~1999-04-06 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-31 9:22 Donn Terry
1999-03-31 10:24 ` Ian Lance Taylor
1999-04-05 8:31 ` Donn Terry
1999-04-05 16:39 ` Philippe De Muyter
1999-04-06 7:55 ` Donn Terry
1999-04-06 8:11 ` Ian Lance Taylor [this message]
1999-04-06 8:20 ` Donn Terry
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).