From: Thiemo Seufer <ths@networkno.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: [rfc] Target-described register support for MIPS
Date: Wed, 13 Jun 2007 15:05:00 -0000 [thread overview]
Message-ID: <20070613150502.GC8584@networkno.de> (raw)
In-Reply-To: <Pine.LNX.4.64N.0706131221130.7198@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Tue, 12 Jun 2007, Daniel Jacobowitz wrote:
>
> > > Hmm, these look wrong -- no "ta" registers have been defined for old
> > > ABIs.
> >
> > OK, I'll drop them. They came from O32_SYMBOLIC_REGISTER_NAMES in
> > gas/config/tc-mips.c.
>
> Hmm, it looks like they may have been defined so that some weird
> handcoded assembly works for both o32 and n32 by using $t0-$t3 and
> $ta0-$ta3 -- note how the definitions are swapped for the two ABIs.
>
> But the names make no sense for o32 -- "ta" stands for
> "temporary/argument" and these are obviously not argument registers. I do
> not recall seeing any code using these names anyway and portable code will
> probably refer to the registers by numbers as $4-$15 (once you have
> recorded or discarded the arguments you are free to use all of these
> registers as temporaries anyway), possibly hiding them under some
> preprocessor macros. And GCC does not care.
The "ta" aliases are supposed to help with writing multi-ABI assembler
code, and are occasionally used for that purpose. I don't think they
are useful for disassembling. When gdb knows the ABI it should IMHO
display the "real" names instead of the "ta" aliases.
Thiemo
next prev parent reply other threads:[~2007-06-13 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:40 Daniel Jacobowitz
2007-06-12 18:14 ` Maciej W. Rozycki
2007-06-12 18:25 ` Daniel Jacobowitz
2007-06-13 11:42 ` Maciej W. Rozycki
2007-06-13 15:05 ` Thiemo Seufer [this message]
2007-06-13 17:37 ` Daniel Jacobowitz
2007-06-13 18:28 ` Daniel Jacobowitz
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=20070613150502.GC8584@networkno.de \
--to=ths@networkno.de \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
/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