From: Carl Love <cel@us.ibm.com>
To: Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org,
UlrichWeigand <Ulrich.Weigand@de.ibm.com>
Cc: cel@us.ibm.com
Subject: RE: [PATCH 2/2] PowerPC, Fix-test-gdb.base-store.exp
Date: Mon, 16 Oct 2023 08:51:53 -0700 [thread overview]
Message-ID: <38350af1796b518994551ea48551fd70d8ef4e37.camel@us.ibm.com> (raw)
In-Reply-To: <878r82hbwl.fsf@redhat.com>
Andrew:
On Mon, 2023-10-16 at 15:36 +0100, Andrew Burgess wrote:
> Carl Love <cel@us.ibm.com> writes:
>
> > GDB maintainers:
> >
> > This is the second patch which fixes the 128-bit floating point
> > register mappings.
> >
<snip>
> > +static struct value *
> > +rs6000_value_from_register (struct gdbarch *gdbarch, struct type
> > *type,
> > + int regnum, struct frame_id frame_id)
> > +{
> > + int len = type->length ();
> > + struct value *value = value::allocate (type);
> > + frame_info_ptr frame;
> > +
> > + /* We have an IEEE 128-bit float need to change regnum mapping
> > from
> > + fpr to vsr. */
> > + regnum = ieee_128_float_regnum_adjust (gdbarch, type, regnum);
> > +
> > + value->set_lval (lval_register);
> > + frame = frame_find_by_id (frame_id);
>
> You can move the declaration of frame to here:
>
> frame_info_ptr frame = frame_find_by_id (frame_id);
OK, fixed.
>
> which is the preferred GDB style these days.
>
> Reviewed-By: Andrew Burgess <aburgess@redhat.com>
>
> Thanks,
> Andrew
>
next prev parent reply other threads:[~2023-10-16 15:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:51 Carl Love
2023-10-12 14:58 ` [Patch 1/2] " Carl Love
2023-10-13 20:34 ` Keith Seitz
2023-10-13 21:00 ` Carl Love
2023-10-16 11:12 ` Ulrich Weigand
2023-10-16 14:31 ` Andrew Burgess
2023-10-16 15:51 ` Carl Love
2023-10-19 15:54 ` Carl Love
2023-10-24 8:50 ` Andrew Burgess
2023-10-24 16:05 ` Carl Love
2023-10-20 18:08 ` [PATCH 1/2, ver2] " Carl Love
2023-10-24 9:30 ` Andrew Burgess
2023-10-25 13:24 ` Ulrich Weigand
2023-10-30 9:45 ` Andrew Burgess
2023-10-30 16:44 ` Ulrich Weigand
2023-10-30 17:16 ` Carl Love
2023-10-30 17:25 ` [PATCH 1/2, ver3] " Carl Love
2023-11-06 18:24 ` Carl Love
2023-11-08 10:54 ` Andrew Burgess
2023-10-12 15:00 ` [PATCH 2/2] " Carl Love
2023-10-13 20:35 ` Keith Seitz
2023-10-13 21:00 ` Carl Love
2023-10-16 11:13 ` Ulrich Weigand
2023-10-16 14:36 ` Andrew Burgess
2023-10-16 15:51 ` Carl Love [this message]
2023-10-20 18:08 ` Carl Love
2023-10-24 8:53 ` Andrew Burgess
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=38350af1796b518994551ea48551fd70d8ef4e37.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).