Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Will Deacon <will@kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/4] kselftest/arm64: Fix compilation warnings/errors in the arm64 tests
Date: Fri, 8 Nov 2024 15:03:43 +0000	[thread overview]
Message-ID: <Zy4oT2w63WGXBASQ@arm.com> (raw)
In-Reply-To: <3f0b7891-7f67-441b-8ba9-ab302ac57792@sirena.org.uk>

On Fri, Nov 08, 2024 at 02:58:34PM +0000, Mark Brown wrote:
> On Fri, Nov 08, 2024 at 01:49:16PM +0000, Catalin Marinas wrote:
> > It looks like people started ignoring the compiler warnings (or even
> > errors) when building the arm64-specific kselftests. The first three
> > patches are printf() arguments adjustment. The last one adds
> > ".arch_extension sme", otherwise they fail to build (with my toolchain
> 
> Unfortunately there's a lot of toolchain variance with these warnings so
> a lot of people simply won't see them, you need a fairly fresh toolchain
> to see them, and IIRC GCC and clang warn about different sets of things
> too which doesn't help.  If you look at the set of tests you're updating
> they're all fairly old so will predate the warnings having been added, I
> doubt anyone touched them recently enough to see the warnings.

But we should still fix them ;). I tried both gcc-12 and clang-14 that
come with my Debian stable installation. If we see others, we'll fix
them in time.

Thanks for the reviews.

-- 
Catalin

  reply	other threads:[~2024-11-08 15:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 13:49 [PATCH 0/4] kselftest/arm64: Fix compilation warnings/errors in the arm64 tests Catalin Marinas
2024-11-08 13:49 ` [PATCH 1/4] kselftest/arm64: Fix printf() compiler warnings in the arm64 fp tests Catalin Marinas
2024-11-08 15:01   ` Mark Brown
2024-11-08 13:49 ` [PATCH 2/4] kselftest/arm64: Fix printf() warning in the arm64 MTE prctl() test Catalin Marinas
2024-11-08 15:10   ` Mark Brown
2024-11-08 15:25     ` Catalin Marinas
2024-11-08 15:30       ` Mark Brown
2024-11-08 15:35         ` Catalin Marinas
2024-11-08 13:49 ` [PATCH 3/4] kselftest/arm64: Fix printf() compiler warnings in the arm64 syscall-abi.c tests Catalin Marinas
2024-11-08 15:04   ` Mark Brown
2024-11-08 13:49 ` [PATCH 4/4] kselftest/arm64: Fix compilation of SME instructions in the arm64 fp tests Catalin Marinas
2024-11-08 14:53   ` Mark Brown
2024-11-08 14:59     ` Catalin Marinas
2024-11-08 14:58 ` [PATCH 0/4] kselftest/arm64: Fix compilation warnings/errors in the arm64 tests Mark Brown
2024-11-08 15:03   ` Catalin Marinas [this message]
2024-11-08 15:16     ` Mark Brown
2024-11-12 16:07 ` (subset) " Catalin Marinas

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=Zy4oT2w63WGXBASQ@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=will@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