From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Willy Tarreau" <w@1wt.eu>, "Shuah Khan" <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 00/15] tools/nolibc: improve LLVM/clang support
Date: Wed, 7 Aug 2024 16:09:41 -0600 [thread overview]
Message-ID: <dc3b8c77-8051-4232-9feb-753ea0b44f4f@linuxfoundation.org> (raw)
In-Reply-To: <20240807-nolibc-llvm-v2-0-c20f2f5fc7c2@weissschuh.net>
On 8/7/24 15:51, Thomas Weißschuh wrote:
> The current support for LLVM and clang in nolibc and its testsuite is
> very limited.
>
> * Various architectures plain do not compile
> * The user *has* to specify "-Os" otherwise the program crashes
> * Cross-compilation of the tests does not work
> * Using clang is not wired up in run-tests.sh
>
> This series extends this support.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Changes in v2:
> - Add support for all architectures
> - powerpc: "selftests/nolibc: don't use libgcc when building with clang"
> - mips: "tools/nolibc: mips: load current function to $t9"
> - s390: "selftests/nolibc: use correct clang target for s390/powerz"
> - Expand commit messages
> - Use __nolibc_ prefix for custom macros
> - Link to v1: https://lore.kernel.org/r/20240728-nolibc-llvm-v1-0-bc384269bc35@weissschuh.net
>
> ---
> Thomas Weißschuh (15):
> tools/nolibc: arm: use clang-compatible asm syntax
> tools/nolibc: mips: load current function to $t9
> tools/nolibc: powerpc: limit stack-protector workaround to GCC
> tools/nolibc: compiler: introduce __nolibc_has_attribute()
> tools/nolibc: move entrypoint specifics to compiler.h
> tools/nolibc: compiler: use attribute((naked)) if available
> selftests/nolibc: report failure if no testcase passed
> selftests/nolibc: avoid passing NULL to printf("%s")
> selftests/nolibc: determine $(srctree) first
> selftests/nolibc: add support for LLVM= parameter
> selftests/nolibc: add cc-option compatible with clang cross builds
> selftests/nolibc: run-tests.sh: avoid overwriting CFLAGS_EXTRA
> selftests/nolibc: don't use libgcc when building with clang
> selftests/nolibc: use correct clang target for s390/powerz
> selftests/nolibc: run-tests.sh: allow building through LLVM
>
> tools/include/nolibc/arch-aarch64.h | 4 +--
> tools/include/nolibc/arch-arm.h | 8 +++---
> tools/include/nolibc/arch-i386.h | 4 +--
> tools/include/nolibc/arch-loongarch.h | 4 +--
> tools/include/nolibc/arch-mips.h | 8 ++++--
> tools/include/nolibc/arch-powerpc.h | 6 ++--
> tools/include/nolibc/arch-riscv.h | 4 +--
> tools/include/nolibc/arch-s390.h | 4 +--
> tools/include/nolibc/arch-x86_64.h | 4 +--
> tools/include/nolibc/compiler.h | 24 +++++++++++-----
> tools/testing/selftests/nolibc/Makefile | 41 +++++++++++++++++++---------
> tools/testing/selftests/nolibc/nolibc-test.c | 4 +--
> tools/testing/selftests/nolibc/run-tests.sh | 16 ++++++++---
> 13 files changed, 83 insertions(+), 48 deletions(-)
> ---
> base-commit: ae1f550efc11eaf1496c431d9c6e784cb49124c5
> change-id: 20240727-nolibc-llvm-3fad68590d4c
>
> Best regards,
Looks good to me. For selftests patches:
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2024-08-07 22:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 21:51 [PATCH v2 00/15] tools/nolibc: improve LLVM/clang support Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 01/15] tools/nolibc: arm: use clang-compatible asm syntax Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 02/15] tools/nolibc: mips: load current function to $t9 Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 03/15] tools/nolibc: powerpc: limit stack-protector workaround to GCC Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 04/15] tools/nolibc: compiler: introduce __nolibc_has_attribute() Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 05/15] tools/nolibc: move entrypoint specifics to compiler.h Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 06/15] tools/nolibc: compiler: use attribute((naked)) if available Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 07/15] selftests/nolibc: report failure if no testcase passed Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 08/15] selftests/nolibc: avoid passing NULL to printf("%s") Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 09/15] selftests/nolibc: determine $(srctree) first Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 10/15] selftests/nolibc: add support for LLVM= parameter Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 11/15] selftests/nolibc: add cc-option compatible with clang cross builds Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 12/15] selftests/nolibc: run-tests.sh: avoid overwriting CFLAGS_EXTRA Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 13/15] selftests/nolibc: don't use libgcc when building with clang Thomas Weißschuh
2024-08-07 21:51 ` [PATCH v2 14/15] selftests/nolibc: use correct clang target for s390/powerz Thomas Weißschuh
2024-08-10 14:54 ` Willy Tarreau
2024-08-07 21:51 ` [PATCH v2 15/15] selftests/nolibc: run-tests.sh: allow building through LLVM Thomas Weißschuh
2024-08-07 22:09 ` Shuah Khan [this message]
2024-08-10 14:57 ` [PATCH v2 00/15] tools/nolibc: improve LLVM/clang support Willy Tarreau
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=dc3b8c77-8051-4232-9feb-753ea0b44f4f@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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