From: Vineet Gupta <vineetg@rivosinc.com>
To: "Christoph Müllner" <christoph.muellner@vrull.eu>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
Darius Rad <darius@bluespec.com>,
Alistair Francis <alistair.francis@wdc.com>,
Vincent Chen <vincent.chen@sifive.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
libc-alpha@sourceware.org, sw-dev@groups.riscv.org
Subject: Re: riscv glibc testing
Date: Fri, 11 Nov 2022 13:14:22 -0800 [thread overview]
Message-ID: <c93e5f60-99e0-d477-8c07-49b83c74a298@rivosinc.com> (raw)
In-Reply-To: <CAEg0e7h8vEk9DA88SeLK8QuLEnki6AOHbQWWHzh00UHoqPEv4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Hi Christoph,
Awesome, that's exactly what I was looking for :-)
I'll give it a try.
Thx,
-Vineet
On 11/11/22 12:46, Christoph Müllner wrote:
> Hi Vineet,
>
> did you see my PR for improved testing capabilities for the
> riscv-gnu-toolchain repo:
> https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1139
>
> Among the changes is support for testing glibc.
> Tests run very long and produce incredibly much output (triggers an
> out-of-memory of tmux on my 32GiB machine).
> Executed everything on a Fedora machine.
>
> BR
> Christoph
>
>
> On Fri, Nov 11, 2022 at 8:48 PM Vineet Gupta <vineetg@rivosinc.com> wrote:
>
> 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
>
prev parent reply other threads:[~2022-11-11 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 19:48 Vineet Gupta
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 [this message]
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=c93e5f60-99e0-d477-8c07-49b83c74a298@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).