From: Vineet Gupta <vineetg@rivosinc.com>
To: "Palmer Dabbelt" <palmer@rivosinc.com>,
"Darius Rad" <darius@bluespec.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Vincent Chen" <vincent.chen@sifive.com>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>
Cc: libc-alpha@sourceware.org, sw-dev@groups.riscv.org
Subject: riscv glibc testing
Date: Fri, 11 Nov 2022 11:48:20 -0800 [thread overview]
Message-ID: <ba944dbb-735c-c7bd-af1e-64213b3b4611@rivosinc.com> (raw)
Hi,
Trying to understand how folks working on riscv glibc run the testsuite.
One could run native on Unmatched (but doesn't allow testing new
extensions) or native on qemu with linux (but that will likely be too
slow) specially the building part.
My preferred solution would be to avoid linux altogether, do a host
cross-build and test with User mode qemu. And then wire it into
riscv-gnu-toolchain [1] just like it currently tests gcc dejagnu.
However glibc cross testing from my prior ARC work required linux+ssh etc.
This email is to see if someone has such as setup already.
Thx,
-Vineet
[1] https://github.com/riscv-collab/riscv-gnu-toolchain
next reply other threads:[~2022-11-11 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 19:48 Vineet Gupta [this message]
2022-11-11 19:51 ` Philipp Tomsich
2022-11-11 20:46 ` Palmer Dabbelt
2022-11-14 19:41 ` DJ Delorie
2022-11-11 20:46 ` Christoph Müllner
2022-11-11 21:14 ` Vineet Gupta
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=ba944dbb-735c-c7bd-af1e-64213b3b4611@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=alistair.francis@wdc.com \
--cc=christoph.muellner@vrull.eu \
--cc=darius@bluespec.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sw-dev@groups.riscv.org \
--cc=vincent.chen@sifive.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 read-only IMAP folder(s) and NNTP newsgroup(s).