From: dj@delorie.com (DJ Delorie)
To: gcc2@cygnus.com, gas2@cygnus.com
Subject: Lxx vs .Lxxx - gcc vs gas
Date: Sat, 17 Jun 1995 14:58:00 -0000 [thread overview]
Message-ID: <199506172158.RAA25682@delorie.com> (raw)
[Be careful when replying; this was sent to two mailing lists - DJ]
There are two types of "local" labels used by gcc and gas:
(1) Lfoo:
(2) .Lfoo:
gcc chooses which to use based on whether the target prepends an
underscore to external symbols or not.
gas chooses which to use based on whether the output object format is
COFF or not (for the i386, at least).
DJGPP is coff with underscores, and the two don't agree on which is
right, so I end up with all the local labels in the object's symbol
table.
Which should I fix? Is there a global solution, or will I need a
special case for djgpp?
DJ
dj@delorie.com
next reply other threads:[~1995-06-17 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-06-17 14:58 DJ Delorie [this message]
1995-06-17 16:33 ` Ken Raeburn
1995-06-17 17:00 ` Ronald F. Guilmette
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=199506172158.RAA25682@delorie.com \
--to=dj@delorie.com \
--cc=gas2@cygnus.com \
--cc=gcc2@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).