Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>, Mark Brown <broonie@kernel.org>,
	kernel@collabora.com, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] selftests: fix LLVM build for i386 and x86_64
Date: Sat, 4 Feb 2023 14:19:48 +0100	[thread overview]
Message-ID: <dae9314b-c99a-bb95-b0ed-f6a8c861d78d@collabora.com> (raw)
In-Reply-To: <YvKOV1L73Mv/Dc6P@dev-arch.thelio-3990X>

Hi Shuah, Nathan,

On 09/08/2022 18:41, Nathan Chancellor wrote:
> On Tue, Aug 09, 2022 at 04:22:31PM +0200, Guillaume Tucker wrote:
>> Add missing cases for the i386 and x86_64 architectures when
>> determining the LLVM target for building kselftest.
>>
>> Fixes: 795285ef2425 ("selftests: Fix clang cross compilation")
>> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> 
> Right, I think this is the correct thing to do for the selftests. For
> the main kernel build, we use CLANG_TARGETS_FLAGS_x86 because ARCH=i386
> and ARCH=x86_64 are covered by SUBARCH=x86, which is what we switch on,
> rather than ARCH. I do see a couple of references to SUBARCH in the
> tools directory but I am not sure if that is usable for this part so:
> 
> Reviewed-by: Nathan Chancellor <nathan@kernel.org>

Thanks for the review.

Could you please apply this patch?  It looks like it was
forgotten like the one with the missing trailing ')' I sent
around that time (now fixed with Mark's patch).

Alternatively, please let me know if anything else needs to be
done for it.

Thanks,
Guillaume

>> ---
>>  tools/testing/selftests/lib.mk | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/tools/testing/selftests/lib.mk b/tools/testing/selftests/lib.mk
>> index b1c62914366b..cc4c443d5b14 100644
>> --- a/tools/testing/selftests/lib.mk
>> +++ b/tools/testing/selftests/lib.mk
>> @@ -10,12 +10,14 @@ endif
>>  CLANG_TARGET_FLAGS_arm          := arm-linux-gnueabi
>>  CLANG_TARGET_FLAGS_arm64        := aarch64-linux-gnu
>>  CLANG_TARGET_FLAGS_hexagon      := hexagon-linux-musl
>> +CLANG_TARGET_FLAGS_i386         := i386-linux-gnu
>>  CLANG_TARGET_FLAGS_m68k         := m68k-linux-gnu
>>  CLANG_TARGET_FLAGS_mips         := mipsel-linux-gnu
>>  CLANG_TARGET_FLAGS_powerpc      := powerpc64le-linux-gnu
>>  CLANG_TARGET_FLAGS_riscv        := riscv64-linux-gnu
>>  CLANG_TARGET_FLAGS_s390         := s390x-linux-gnu
>>  CLANG_TARGET_FLAGS_x86          := x86_64-linux-gnu
>> +CLANG_TARGET_FLAGS_x86_64       := x86_64-linux-gnu
>>  CLANG_TARGET_FLAGS              := $(CLANG_TARGET_FLAGS_$(ARCH))
>>  
>>  ifeq ($(CROSS_COMPILE),)
>> -- 
>> 2.30.2
>>


      reply	other threads:[~2023-02-04 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 14:22 [PATCH] selftests: fix LLVM build for i386 and x86_64 Guillaume Tucker
2022-08-09 16:41 ` Nathan Chancellor
2023-02-04 13:19   ` Guillaume Tucker [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=dae9314b-c99a-bb95-b0ed-f6a8c861d78d@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=broonie@kernel.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=shuah@kernel.org \
    --cc=trix@redhat.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