From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: deuling@de.ibm.com (Markus Deuling),
gdb-patches@sourceware.org (GDB Patches),
eliz@gnu.org (Eli Zaretskii),
brobecker@adacore.com (Joel Brobecker),
jimb@codesourcery.com (Jim Blandy),
rearnsha@arm.com, mark.kettenis@xs4all.nl (Mark Kettenis)
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Tue, 09 Oct 2007 20:03:00 -0000 [thread overview]
Message-ID: <200710091959.l99Jxdqp015297@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071008141039.GA12235@caradoc.them.org> from "Daniel Jacobowitz" at Oct 08, 2007 10:10:39 AM
Daniel Jacobowitz wrote:
> On Mon, Oct 08, 2007 at 04:01:36PM +0200, Ulrich Weigand wrote:
> > Agreed for that particular usage. In general, the reg_to_regnum
> > routines should probably still be converted to "m" -- e.g. the
> > rs6000 versions do make non-trivial use of the gdbarch ...
>
> Isn't that problematic? We do not know what the architecture will
> be at this point. Only the bits common to all architectures using
> the same init routine are safe to use.
Hmm, good point, I'll have to think about this ...
> As for the rs6000 version, the patches I posted last week allow a
> followup patch which propogates some constants. Most of the values
> being read from the tdep are now constants. Some (e.g. ppc_mq_regnum)
> are not constants, but have either a single constant value or -1 if
> the register is not present; for those the constant is appropriate
> in the reg_to_regnum routines anyway.
I agree that everything would be much easier if the register numbers
were constants. But note that rs6000 is not the only platform where
this is not the case, I see the same (or even worse) also in mips,
m32c, xtensa, ... (The mep usage also seems suspicious.)
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-10-09 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 8:18 Markus Deuling
2007-10-08 13:03 ` Ulrich Weigand
2007-10-08 13:22 ` Markus Deuling
2007-10-08 13:35 ` Daniel Jacobowitz
2007-10-08 14:01 ` Ulrich Weigand
2007-10-08 14:10 ` Daniel Jacobowitz
2007-10-09 20:03 ` Ulrich Weigand [this message]
2007-10-09 21:39 ` Daniel Jacobowitz
2007-10-10 11:54 ` Mark Kettenis
2007-10-10 12:01 ` Daniel Jacobowitz
2007-10-08 13:16 ` Joel Brobecker
2007-10-09 7:02 ` Markus Deuling
2007-10-08 17:53 ` Maxim Grigoriev
2007-10-09 5:10 ` Markus Deuling
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=200710091959.l99Jxdqp015297@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=rearnsha@arm.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