From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Markus Deuling <deuling@de.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
Jim Blandy <jimb@codesourcery.com>,
rearnsha@arm.com, Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Tue, 09 Oct 2007 21:39:00 -0000 [thread overview]
Message-ID: <20071009200321.GA4564@caradoc.them.org> (raw)
In-Reply-To: <200710091959.l99Jxdqp015297@d12av02.megacenter.de.ibm.com>
On Tue, Oct 09, 2007 at 09:59:39PM +0200, Ulrich Weigand wrote:
> 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.)
Yes. For some platforms (xtensa, mep) there may not be much we can
do... and MIPS presents its own unique problems because of the use
of pseudo registers for everything. Hmm, this makes me wonder how
deep the broken goes. Maybe we shouldn't translate from DWARF numbers
to internal ones until later.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-09 20:03 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
2007-10-09 21:39 ` Daniel Jacobowitz [this message]
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=20071009200321.GA4564@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=rearnsha@arm.com \
--cc=uweigand@de.ibm.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