From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] MIPS: MIPS_LAST_FP_ARG_REGNUM, MIPS_LAST_ARG_REGNUM changes
Date: Wed, 21 May 2003 16:37:00 -0000 [thread overview]
Message-ID: <1030521163655.ZM31364@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [RFA] MIPS: MIPS_LAST_FP_ARG_REGNUM, MIPS_LAST_ARG_REGNUM changes" (May 21, 12:17pm)
On May 21, 12:17pm, Andrew Cagney wrote:
> > This is patch 2 of many more to come. It depends upon
> > http://sources.redhat.com/ml/gdb-patches/2003-05/msg00268.html.
> >
> > Okay?
>
> Per my earlier comment, I don't think this one is right. I don't think
> things like LAST_ARG_REGNUM belong in that cooked/raw reg structure.
> Instead, they should exist out side it.
>
> If the code really wants to differentiate between the raw and cooked
> register number, why not use the more explicit:
>
> rawnum->gp0_regnum + tdep->last_arg_regnum
So, last_arg_regnum represents a count of the number of argument
registers?
That's fine (at the moment anyway) for the GPRs, but it doesn't work
for the FPRs. For o32, I have things arranged so that there are a
total of 16 cooked FPRs and 32 raw FPRs. Therefore, argument register
counts will be different between cooked vs raw. IMO, it really does
make sense to put these values into the cooked/raw structure. I'm
having difficulty understanding why you're objecting to this layout.
Kevin
next prev parent reply other threads:[~2003-05-21 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 21:51 Kevin Buettner
2003-05-21 16:17 ` Andrew Cagney
2003-05-21 16:37 ` Kevin Buettner [this message]
2003-05-21 18:07 ` Andrew Cagney
2003-05-21 18:16 ` Kevin Buettner
2003-05-21 19:13 ` 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=1030521163655.ZM31364@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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