From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH 0/3] selftests/nolibc: enable qemu-system tests with LLVM builds
Date: Mon, 21 Jul 2025 04:57:30 +0200 [thread overview]
Message-ID: <20250721025730.GC1886@1wt.eu> (raw)
In-Reply-To: <20250719-nolibc-llvm-system-v1-0-1730216ce171@weissschuh.net>
On Sat, Jul 19, 2025 at 05:38:26PM +0200, Thomas Weißschuh wrote:
> Currently the test setup does not support running nolibc-test built with
> LLVM in qemu-system. Enable this.
>
> FYI, sparc32 on LLVM seems to be broken at the moment. To me this looks
> like a LLVM regression, emitting invalid object code.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
For the series, once the help message is adjusted:
Acked-by: Willy Tarreau <w@1wt.eu>
Thanks!
Willy
prev parent reply other threads:[~2025-07-21 2:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 15:38 [PATCH 0/3] selftests/nolibc: enable qemu-system tests with LLVM builds Thomas Weißschuh
2025-07-19 15:38 ` [PATCH 1/3] selftests/nolibc: deduplicate invocations of toplevel Makefile Thomas Weißschuh
2025-07-19 15:38 ` [PATCH 2/3] selftests/nolibc: don't pass CC to " Thomas Weißschuh
2025-07-21 2:56 ` Willy Tarreau
2025-08-17 8:30 ` Thomas Weißschuh
2025-08-17 9:39 ` Willy Tarreau
2025-08-18 14:07 ` Thomas Weißschuh
2025-08-19 3:54 ` Willy Tarreau
2025-07-19 15:38 ` [PATCH 3/3] selftests/nolibc: always compile the kernel with GCC Thomas Weißschuh
2025-07-21 2:57 ` Willy Tarreau [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=20250721025730.GC1886@1wt.eu \
--to=w@1wt.eu \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=shuah@kernel.org \
/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).