From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Jeff Law <jlaw@ventanamicro.com>,
Vineet Gupta <vineetg@rivosinc.com>,
kevinl@rivosinc.com, gcc-patches@gcc.gnu.org,
Kito Cheng <kito.cheng@gmail.com>,
jiawei@iscas.ac.cn, christoph.muellner@vrull.eu
Subject: Re: RISC-V Test Errors and Failures
Date: Tue, 16 May 2023 22:08:14 -0600 [thread overview]
Message-ID: <71bc3fed-d273-d52e-75dd-18ff91eed741@gmail.com> (raw)
In-Reply-To: <mhng-7713e018-8a46-49cb-ae5f-0efe51078141@palmer-ri-x1c9a>
On 5/16/23 20:39, Palmer Dabbelt wrote:
>
> By "chroot environment" you mean something like a
> debootstrap-into-chroot with qemu-user/binfmt-misc? I don't have that
> setup right now, but it wouldn't be a big lift.
Essentially, yes. I actually have a home built ones for the various
targets. There was a time when they needed to be <100M so they could be
stored on github. Going forward I just want them to be a docker
container for Fedora or Ubuntu. With binfmt you can run non-native
containers trivially.
jeff
next prev parent reply other threads:[~2023-05-17 4:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 23:06 Palmer Dabbelt
2023-05-17 0:16 ` Vineet Gupta
2023-05-17 0:20 ` Palmer Dabbelt
2023-05-17 1:04 ` Vineet Gupta
2023-05-17 1:29 ` Palmer Dabbelt
2023-05-17 2:00 ` Jeff Law
2023-05-17 2:05 ` Palmer Dabbelt
2023-05-17 2:32 ` Jeff Law
2023-05-17 2:39 ` Palmer Dabbelt
2023-05-17 4:08 ` Jeff Law [this message]
2023-05-17 2:08 ` Vineet Gupta
2023-05-17 2:12 ` Jeff Law
2023-05-17 7:52 ` Andreas Schwab
2023-05-19 0:13 ` Vineet Gupta
2023-05-25 20:29 ` Thomas Schwinge
2023-05-26 0:04 ` Vineet Gupta
2023-05-17 1:57 juzhe.zhong
2023-05-17 2:02 ` Andrew Pinski
2023-05-17 2:07 juzhe.zhong
2023-05-17 2:13 ` Palmer Dabbelt
2023-05-17 2:20 ` Kito Cheng
2023-05-17 2:21 ` Kito Cheng
2023-05-17 2:46 ` Vineet Gupta
2023-05-17 2:47 ` Palmer Dabbelt
2023-05-17 2:51 ` Patrick O'Neill
2023-05-17 2:53 ` Palmer Dabbelt
2023-05-17 3:08 ` Vineet Gupta
2023-05-17 3:11 ` Palmer Dabbelt
2023-05-17 3:33 ` Kito Cheng
2023-05-17 4:04 ` Jeff Law
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=71bc3fed-d273-d52e-75dd-18ff91eed741@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=jlaw@ventanamicro.com \
--cc=kevinl@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=vineetg@rivosinc.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).