From: Richard Henderson <richard.henderson@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Nicholas Piggin <npiggin@gmail.com>
Cc: qemu-riscv@nongnu.org, "Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
qemu-devel@nongnu.org, "Chao Liu" <chao.liu@zevorn.cn>,
"Nicholas Joaquin" <njoaquin@tenstorrent.com>,
"Ganesh Valliappan" <gvalliappan@tenstorrent.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/3] target/risvc: Fix vector whole ldst vstart check
Date: Fri, 5 Sep 2025 09:18:11 +0200 [thread overview]
Message-ID: <188f0525-154e-4d08-a155-68e8800e302d@linaro.org> (raw)
In-Reply-To: <3dd9888f-be16-48f8-a858-f58a5b57825d@ventanamicro.com>
On 9/4/25 13:06, Daniel Henrique Barboza wrote:
> How hard it is to update the GCC version we're running in the docker images for
> "check-tcg"? We would like to use a RISC-V vector header that isn't supported
> ATM.
If debian packages the gcc version, then it's easy: change
gcc-riscv-linux-gnu
to
gcc-NN-riscv-linux-gnu
If the version isn't packaged, then it's harder, and we would need to either build our own
gcc within the container (see dockerfiles/debian-microblaze-cross.d/build-toolchain.sh),
or you can host a pre-built version somewhere (see dockerfiles/debian-loongarch-cross.docker).
r~
next prev parent reply other threads:[~2025-09-05 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 3:01 [PATCH 0/3] target/riscv: corner case fixes Nicholas Piggin
2025-09-03 3:01 ` [PATCH 1/3] target/riscv: Fix IALIGN check in misa write Nicholas Piggin
2025-09-03 17:19 ` Daniel Henrique Barboza
2025-09-03 3:01 ` [PATCH 2/3] target/risvc: Fix vector whole ldst vstart check Nicholas Piggin
2025-09-03 20:13 ` Daniel Henrique Barboza
2025-09-04 5:16 ` Nicholas Piggin
2025-09-04 11:06 ` Daniel Henrique Barboza
2025-09-05 7:18 ` Richard Henderson [this message]
2025-09-17 13:44 ` Joel Stanley
2025-09-17 13:53 ` Daniel P. Berrangé
2025-09-03 3:01 ` [PATCH 3/3] tests/tcg: Add riscv test for interrupted vector ops Nicholas Piggin
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=188f0525-154e-4d08-a155-68e8800e302d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=chao.liu@zevorn.cn \
--cc=dbarboza@ventanamicro.com \
--cc=gvalliappan@tenstorrent.com \
--cc=liwei1518@gmail.com \
--cc=njoaquin@tenstorrent.com \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).