From: Daniel Jacobowitz <drow@mvista.com>
To: Richard.Earnshaw@arm.com
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: Non-multiarched macros
Date: Fri, 01 Feb 2002 09:08:00 -0000 [thread overview]
Message-ID: <20020201120846.A27564@nevyn.them.org> (raw)
In-Reply-To: <200202011703.RAA16938@cam-mail2.cambridge.arm.com>
On Fri, Feb 01, 2002 at 05:03:51PM +0000, Richard Earnshaw wrote:
>
> > > 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.
Yep. All the standard formats - including at least ELF and COFF -
will always be available, and no one really plans to change that.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-01 17:08 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 [this message]
2002-02-01 9:27 ` Andrew Cagney
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=20020201120846.A27564@nevyn.them.org \
--to=drow@mvista.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.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