From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH][GDB] aarch64: Add named flags for FPCR and FPSR registers
Date: Thu, 26 Nov 2020 09:06:48 -0300 [thread overview]
Message-ID: <68aed4c3-2e21-a5ad-8c14-f47d83f70c4a@linaro.org> (raw)
In-Reply-To: <VI1PR08MB4061FF4CA78043C50F44FB93E4F90@VI1PR08MB4061.eurprd08.prod.outlook.com>
Hi,
On 11/26/20 6:20 AM, Przemyslaw Wirkus wrote:
> This patch updates FPCR (Floating-point Control Register) and FPSR
> (Floating-point Status Register) named fields in AArch64. For detailed
> description of named register FPCR and FPSR bit fields see [1] and [2].
>
> Please not that bit fields FIZ, AH and NEP (bits 0, 1 and 2 respectively) in
> FPCR are defined starting from Armv8.7 architecture.
>
> [1]: https://developer.arm.com/docs/ddi0595/i/aarch64-system-registers/fpcr
> [2]: https://developer.arm.com/docs/ddi0595/i/aarch64-system-registers/fpsr
>
> Example:
> $ cat -n test.c
> 1 float foo(float pi, float r) {
> 2 return pi * r * r;
> 3 }
> 4
> 5 int main() {
> 6 foo(3.14, 1.725);
> 7 return 0;
> 8 }
>
> $ gcc -O0 -g3 test.c -o test
>
> Before patch (step to line 7):
>>>> info all-registers fpsr
> fpsr 0x10 16
>>>> info all-registers fpcr
> fpcr 0x0 0
>
> After patch:
>>>> info all-registers fpsr
> fpsr 0x10 [ IXC ]
>>>> info all-registers fpcr
> fpcr 0x0 [ RMode=0 ]
>
> OK for master ?
>
> gdb/ChangeLog:
>
> 2020-11-25 Przemyslaw Wirkus <przemyslaw.wirkus@arm.com>
>
> * features/aarch64-fpu.c (create_feature_aarch64_fpu): Regenerate.
> * features/aarch64-fpu.xml: Add named FPCR and FPSR register bit-fields.
>
This is OK. Thanks!
next prev parent reply other threads:[~2020-11-26 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 9:20 Przemyslaw Wirkus via Gdb-patches
2020-11-26 12:06 ` Luis Machado via Gdb-patches [this message]
2020-11-26 12:13 ` Przemyslaw Wirkus via Gdb-patches
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=68aed4c3-2e21-a5ad-8c14-f47d83f70c4a@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=Przemyslaw.Wirkus@arm.com \
--cc=luis.machado@linaro.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