From: Martin Dorey <Martin.Dorey@Madge.com>
To: binutils@sourceware.cygnus.com
Cc: Ian Lance Taylor <ian@zembu.com>
Subject: RE: binutils patches for basic generic i960-elf
Date: Tue, 17 Aug 1999 02:36:00 -0000 [thread overview]
Message-ID: <4110BC526A58D211B56C0000F6B9636D01F58137@ws-exch01.dev.madge.com> (raw)
> My bfd config uses the generic linker - it doesn't provide an
> i960-elf-specific backend relocate_section().
> In general, I recommend writing this. Without it, you won't get many
> of the features of the ELF linker.
Que? bfdint.texi recommends this on the grounds of efficiency and the
ability to handle dynamic linking, neither of which I'm particularly
bothered about for this target. Is there anything else I'm missing out on
by not defining the processor-specific stuff?
> I wonder if it is really correct to discard link once sections when
> doing a relocateable link.
Say all the .linkonce.t.baz sections are combined into .text. How is the
final link then going to know which bits to discard? Or how would you
handle the multiple .linkonce.t.baz sections in the relocatable output?
> Incidentally, I recently fixed a long standing bug in gas to stop it
> from outputting relocs against local symbols in linkonce sections.
> This may work around your problem in a different way.
Doh! Why didn't I ask earlier?
--
next reply other threads:[~1999-08-17 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 2:36 Martin Dorey [this message]
1999-08-17 11:20 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
1999-07-01 0:00 Martin Dorey
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor
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=4110BC526A58D211B56C0000F6B9636D01F58137@ws-exch01.dev.madge.com \
--to=martin.dorey@madge.com \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).