From: Jeffrey A Law <law@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: alan@linuxcare.com.au, binutils@sourceware.cygnus.com
Subject: Re: Unique section ids
Date: Thu, 06 Jul 2000 10:58:00 -0000 [thread overview]
Message-ID: <11454.962906329@upchuck> (raw)
In-Reply-To: <200007061729.KAA32533@elmo.cygnus.com>
In message < 200007061729.KAA32533@elmo.cygnus.com >you write:
> Why can't you append the section name and input file name ? That way
> the (extended) local names would stay the same even if the link order
> is changed on the command line, something that would not happen with
> your unique section id scheme...
You'll need full paths, not just the input file name -- ie, it is possible
to have "foobar.o" appear multiple times like
gcc -o blah foobar.o frob/foobar.o
Which brings up questions like what are valid characters -- filenames could
have embedded spaces, control chars, etc etc.
I mildly prefer the sequence #s approach. But I can live with either.
jeff
next prev parent reply other threads:[~2000-07-06 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 10:29 Nick Clifton
2000-07-06 10:58 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-06 11:27 Nick Clifton
2000-07-08 5:16 ` Alan Modra
2000-07-05 21:00 Alan Modra
2000-07-06 10:09 ` Jeffrey A Law
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=11454.962906329@upchuck \
--to=law@cygnus.com \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=nickc@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).