From: Jerry Zhang Jian <jerry.zhangjian@sifive.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Radkin Kirill <hokeygo@gmail.com>,
gdb-patches@sourceware.org,
Bergner Peter <bergner@oss.tenstorrent.com>,
Matyukevich Sergey <geomatsi@gmail.com>,
Schuchardt Heinrich <heinrich.schuchardt@canonical.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v2 1/3] RISC-V Vector Extension Support
Date: Tue, 13 Oct 2026 22:19:43 +0800 [thread overview]
Message-ID: <EBAEE010-06B2-44FD-BC9C-0D7B1D484A2B@sifive.com> (raw)
In-Reply-To: <874iepaei7.fsf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Hi Andrew,
I didn’t hit that assertion on my end. Would you mind to share your QEMU commands?
BRs
Jerry
> On Oct 13, 2026, at 21:58, Andrew Burgess <aburgess@redhat.com> wrote:
>
> I started looking at this today, I ran into this assertion while running
> the test gdb.arch/riscv-vector-abi-full.exp:
>
> ../../src/gdb/riscv-linux-nat.c:399: internal-error: fetch_registers: Assertion `vregs_state->vlenb == vecreg_size' failed.
>
> If you can confirm that this test runs fine for you then I'll take a
> look at why this might be failing for me.
[-- Attachment #2: Type: text/html, Size: 5176 bytes --]
next prev parent reply other threads:[~2026-10-13 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 17:29 [PATCH v2 0/3] RISC-V Vector Extension support Kirill Radkin
2026-09-25 17:29 ` [PATCH v2 1/3] RISC-V Vector Extension Support Kirill Radkin
2026-10-08 19:44 ` Andrew Burgess
2026-10-08 19:52 ` Jerry Zhang Jian
2026-10-13 13:58 ` Andrew Burgess
2026-10-13 14:19 ` Jerry Zhang Jian [this message]
2026-10-14 3:21 ` Maciej W. Rozycki
2026-09-25 17:29 ` [PATCH v2 2/3] Reverse execution support for RISC-V Vector Extension Kirill Radkin
2026-09-25 17:29 ` [PATCH v2 3/3] RISC-V Vector Extension Support Testing Kirill Radkin
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=EBAEE010-06B2-44FD-BC9C-0D7B1D484A2B@sifive.com \
--to=jerry.zhangjian@sifive.com \
--cc=aburgess@redhat.com \
--cc=bergner@oss.tenstorrent.com \
--cc=gdb-patches@sourceware.org \
--cc=geomatsi@gmail.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=hokeygo@gmail.com \
--cc=palmer@dabbelt.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