From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Moving to GDB_MULTI_ARCH_PARTIAL
Date: Thu, 07 Feb 2002 23:08:00 -0000 [thread overview]
Message-ID: <3C637933.7060502@cygnus.com> (raw)
In-Reply-To: <3C6349CB.5080700@cygnus.com>
> In the mean time I'll re-build everything :-/
i386-aout:
gdbarch.h:1147: #error "Non multi-arch definition of REGISTER_CONVERTIBLE"
gdbarch.h:1151: warning: `REGISTER_CONVERTIBLE' redefined
tm.h:215: warning: this is the location of the previous definition
gdbarch.h:1375: #error "Non multi-arch definition of PUSH_ARGUMENTS"
gdbarch.h:1379: warning: `PUSH_ARGUMENTS' redefined
tm.h:242: warning: this is the location of the previous definition
looking around:
tm-i386.h:#define REGISTER_CONVERTIBLE(regnum) i386_register_convertible (regnum)
tm-ptx.h:#undef REGISTER_CONVERTIBLE
tm-ptx.h:#define REGISTER_CONVERTIBLE(N) \
tm-symmetry.h:#undef REGISTER_CONVERTIBLE
tm-symmetry.h:#define REGISTER_CONVERTIBLE(N) \
this suggests REGISTER_CONVERTIBLE doesn't need to be immediatly converted.
However, it also explains why, at level one, it isn't strict about
overriding macros. Given a case like the i386, the base cpu may be
multi-arched but the variants (tm-ptx.h and tm-symmetry.h) may not.
This again lets them continue to build and work.
Andrew
next prev parent reply other threads:[~2002-02-08 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 9:21 Richard Earnshaw
2002-02-07 19:45 ` Andrew Cagney
2002-02-07 23:08 ` Andrew Cagney [this message]
2002-02-08 1:38 ` Richard Earnshaw
2002-02-08 7:19 ` 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=3C637933.7060502@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