From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] Look for FIR in the last FreeBSD/mips floating-point register.
Date: Tue, 06 Jun 2017 17:49:00 -0000 [thread overview]
Message-ID: <5015074.IOQvVsxonZ@ralph.baldwin.cx> (raw)
In-Reply-To: <bc561f0f53aa3438138166459bbf398e@polymtl.ca>
On Monday, June 05, 2017 10:27:48 PM Simon Marchi wrote:
> On 2017-05-31 18:58, John Baldwin wrote:
> > + for (i = 0; i < 32; i++)
> > + if (regnum == fp0num + i || regnum == -1)
> > + mips_fbsd_collect_reg (regcache, fp0num + i,
> > + regs + i * regsize, regsize);
> > + if (regnum == mips_regnum (gdbarch)->fp_control_status || regnum ==
> > -1)
> > + mips_fbsd_collect_reg (regcache, mips_regnum
> > (gdbarch)->fp_control_status,
> > + regs + 32 * regsize, regsize);
> > + if (regnum == mips_regnum (gdbarch)->fp_implementation_revision
> > + || regnum == -1)
> > + mips_fbsd_collect_reg (regcache,
> > + mips_regnum (gdbarch)->fp_implementation_revision,
> > + regs + 33 * regsize, regsize);
>
> I'm just curious to know why you changed this. They previous code
> assumed that the 32 floating-point registers and the control register
> were contiguous their numbering. Is this no longer true with the new
> register, or is it just for clarity that you separately handle the
> different kinds of registers?
Just for clarity. mips-tdep.c does happen to layout the registers such
that fsr and fir are consecutive after fp31, but fsr and fir do have
separate entries in the mips_regnum structure.
--
John Baldwin
next prev parent reply other threads:[~2017-06-06 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:58 John Baldwin
2017-06-05 20:27 ` Simon Marchi
2017-06-06 17:49 ` John Baldwin [this message]
2017-06-08 7:15 ` Maciej W. Rozycki
2017-06-12 18:47 ` John Baldwin
2017-06-12 20:23 ` Maciej W. Rozycki
2017-06-13 16:43 ` John Baldwin
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=5015074.IOQvVsxonZ@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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