From: Simon Marchi <simark@simark.ca>
To: srinath.parvathaneni@arm.com, gdb-patches@sourceware.org
Cc: guinevere@redhat.com, thiago.bauermann@linaro.org,
luis.machado.foss@gmail.com, Ezra.Sitorus@arm.com
Subject: Re: [PATCH v1] gdb: Fix assignment to TYPE_CODE_FLAGS registers
Date: Mon, 13 Jul 2026 08:26:30 -0400 [thread overview]
Message-ID: <cf6a5838-2de3-414c-b9c6-8076b24b78fa@simark.ca> (raw)
In-Reply-To: <20260713091126.2914903-1-srinath.parvathaneni@arm.com>
On 7/13/26 5:11 AM, srinath.parvathaneni@arm.com wrote:
> From: Srinath Parvathaneni <srinath.parvathaneni@arm.com>
>
> GDB reports "Invalid cast" when assigning small integer literals (32-bit) to
> 64-bit TYPE_CODE_FLAGS registers. For example, with the existing upstream FPMR
> register, set $fpmr = 0x777777777 succeeds, whereas set $fpmr = 0x77 fails with
> "Invalid cast" and this patch fixes the issue but makes changes to a generic
> function value_cast in gdb/valops.c.
>
> * testsuite/gdb.arch/aarch64-fpmr.exp : Add "set $fpmr" test.
> * gdb/valops.c (value_cast): Add TYPE_CODE_FLAGS condition to integer
> assignment.
>
> Regression tested on aarch64-none-linux-gnu with no regressions.
>
> Ok for GDB master?
This seems fine to me, but I am not as confident with this value_cast
code as I am with other things, so I'll give you the:
Approved-By: Simon Marchi <simon.marchi@efficios.com>
but wait ~1 week before pushing in case someone sees something I don't.
Simon
next prev parent reply other threads:[~2026-07-13 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 9:11 srinath.parvathaneni
2026-07-13 12:26 ` Simon Marchi [this message]
2026-07-13 13:37 ` Aktemur, Baris
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=cf6a5838-2de3-414c-b9c6-8076b24b78fa@simark.ca \
--to=simark@simark.ca \
--cc=Ezra.Sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=luis.machado.foss@gmail.com \
--cc=srinath.parvathaneni@arm.com \
--cc=thiago.bauermann@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