From: Richard Henderson <rth@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Where to put per-target global BFD data ?
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990620164714.B4699@cygnus.com> (raw)
In-Reply-To: <199906180941.KAA12938@pathia.cygnus.co.uk>
On Fri, Jun 18, 1999 at 10:41:18AM +0100, Nick Clifton wrote:
> This fails however, when the output format is not the same as the
> input format.
Yep. I have the same problem in elf64-alpha.
My stance at this point is "Don't Do That".
> I am not sure how this can be fixed. I think using the hash table
> may not be the best way to store global information, because of this
> problem, and that another solution needs to be found.
My solution would be to outlaw linking together different formats,
and that the output format must match the input format. Diddling
different formats is what objcopy is for.
r~
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Nick Clifton
1999-07-01 0:00 ` Richard Henderson [this message]
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` Ian Lance Taylor
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=19990620164714.B4699@cygnus.com \
--to=rth@cygnus.com \
--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).