From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Sameer Natu <snatu@whileone.in>
Cc: Greg Savin <greg.savin@sifive.com>,
gdb-patches@sourceware.org, Andrew Burgess <aburgess@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Soham Gargote <sgargote@whileone.in>,
Kirill Radkin <kirill.radkin@syntacore.com>,
Charlie Jenkins <thecharlesjenkins@gmail.com>
Subject: Re: [PATCH] RISC-V: support for vector register accesses via ptrace() in RISC-V Linux native
Date: Sat, 12 Sep 2026 10:03:15 +0200 [thread overview]
Message-ID: <b2312463-44de-42d1-91b9-4f19ceebc706@canonical.com> (raw)
In-Reply-To: <bebd0270-65d2-40a6-ac00-05da6fc25a15@canonical.com>
On 9/12/26 09:37, Heinrich Schuchardt wrote:
>> + if (regnum == RISCV_CSR_VXRM_REGNUM)
>> + {
>> + /* Overwrite VCSR with the VXRM bit here. */
>> + gdb_byte *buf = (gdb_byte *) &vxsat_from_regcache;
I guess the typo is here
%s/vxsat_from_regcache/vxrm_from_regcache/
Best regards
Heinrich
>> + regcache->raw_collect (RISCV_CSR_VXRM_REGNUM, buf);
>> + vregs->vstate.vcsr &= ~((uint64_t) VCSR_MASK_VXRM <<
>> VCSR_POS_VXRM);
>> + vregs->vstate.vcsr |= ((vxrm_from_regcache & VCSR_MASK_VXRM)
>> + << VCSR_POS_VXRM);
>
> vxrm_from_regcache is never initialized. So you are using a random value
> from the stack. Can we completely remove the variable?
next prev parent reply other threads:[~2026-09-12 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:52 Sameer Natu
2025-11-07 17:25 ` RISC-V Vector Extension Support Kirill Radkin
2026-09-12 7:37 ` [PATCH] RISC-V: support for vector register accesses via ptrace() in RISC-V Linux native Heinrich Schuchardt
2026-09-12 8:03 ` Heinrich Schuchardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 23:01 Greg Savin via Gdb-patches
2023-08-04 0:21 ` John Baldwin
2023-08-09 9:21 ` Maciej W. Rozycki
2023-08-09 18:11 ` Greg Savin via Gdb-patches
2023-08-09 23:09 ` Maciej W. Rozycki
2023-08-10 10:35 ` Andy Chiu via Gdb-patches
2023-08-10 11:40 ` Maciej W. Rozycki
2023-08-10 13:55 ` Maciej W. Rozycki
2023-08-10 17:23 ` Andy Chiu via Gdb-patches
2023-08-10 21:08 ` Palmer Dabbelt
2023-08-10 21:21 ` Maciej W. Rozycki
2023-08-11 11:28 ` Andy Chiu via Gdb-patches
2023-08-10 14:05 ` Andy Chiu via Gdb-patches
2023-08-10 20:51 ` Maciej W. Rozycki
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=b2312463-44de-42d1-91b9-4f19ceebc706@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=greg.savin@sifive.com \
--cc=kirill.radkin@syntacore.com \
--cc=palmer@dabbelt.com \
--cc=sgargote@whileone.in \
--cc=snatu@whileone.in \
--cc=thecharlesjenkins@gmail.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