From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Non-multiarched macros
Date: Fri, 01 Feb 2002 09:27:00 -0000 [thread overview]
Message-ID: <3C5ACFE2.6030409@cygnus.com> (raw)
In-Reply-To: <200202011703.RAA16938@cam-mail2.cambridge.arm.com>
>> ELF_MAKE_MSYMBOL_SPECIAL -- elfread.c
>>
>> REGISTER_BYTES_OK
>>
>> > COFF_MAKE_MSYMBOL_SPECIAL -- coffread.c
>>
>> REGISTER_BYTES_OK
>
>
> These two are my biggest concern. They are likely to pull object-format
> specific information into the tdep file. Is that safe? Can I be sure
> that the all the object formats will be available there, regardless of
> configuration.
Dan answered the technical question.
Anyway, it is probably a design flaw (?) and multi-arch conversions
ignore flaws in the design. You can grit your teath and do the
conversion anyway :-)
The rationale is two fold. If people tried to fix every design flaw
they found during the conversion process then the conversion process
would never be finished. Once everything is converted, it is going to
be far easier for someone to go through all targets and test/fix the
design problems.
enjoy,
Andrew
prev parent reply other threads:[~2002-02-01 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 6:07 Richard Earnshaw
2002-02-01 8:26 ` Andrew Cagney
2002-02-01 9:04 ` Richard Earnshaw
2002-02-01 9:08 ` Daniel Jacobowitz
2002-02-01 9:27 ` Andrew Cagney [this message]
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=3C5ACFE2.6030409@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.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