From: John Hubbard <jhubbard@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Beau Belgrave <beaub@linux.microsoft.com>,
Steven Rostedt <rostedt@goodmis.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Justin Stitt <justinstitt@google.com>,
Bill Wendling <morbo@google.com>,
sunliming <sunliming@kylinos.cn>,
Masami Hiramatsu <mhiramat@kernel.org>,
Valentin Obst <kernel@valentinobst.de>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: [PATCH v2 1/2] selftests/lib.mk: handle both LLVM=1 and CC=clang builds
Date: Mon, 3 Jun 2024 10:09:53 -0700 [thread overview]
Message-ID: <96216e54-ba8f-4fd7-b95a-13477c143575@nvidia.com> (raw)
In-Reply-To: <306eebf8-bb5d-4e1a-9fa3-ad3f4ea11b9c@sirena.org.uk>
On 6/3/24 8:32 AM, Mark Brown wrote:
> On Fri, May 31, 2024 at 11:37:50AM -0700, John Hubbard wrote:
>> The kselftests may be built in a couple different ways:
>> make LLVM=1
>> make CC=clang
>>
>> In order to handle both cases, set LLVM=1 if CC=clang. That way,the rest
>> of lib.mk, and any Makefiles that include lib.mk, can base decisions
>> solely on whether or not LLVM is set.
>
> ICBW but I believe there are still some architectures with clang but not
> lld support where there's a use case for using CC=clang.
I'm inclined to wait for those to make themselves known... :)
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-06-03 17:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 18:37 [PATCH v2 0/2] selftests/lib.mk: LLVM=1, CC=clang, and warnings John Hubbard
2024-05-31 18:37 ` [PATCH v2 1/2] selftests/lib.mk: handle both LLVM=1 and CC=clang builds John Hubbard
2024-06-03 15:32 ` Mark Brown
2024-06-03 17:09 ` John Hubbard [this message]
2024-06-03 20:11 ` John Hubbard
2024-06-03 22:47 ` Nathan Chancellor
2024-06-04 4:55 ` John Hubbard
2024-06-07 11:12 ` Ryan Roberts
2024-06-07 17:15 ` Nathan Chancellor
2024-06-07 20:13 ` John Hubbard
2024-06-04 13:14 ` Mark Brown
2024-05-31 18:37 ` [PATCH v2 2/2] selftests/lib.mk: silence some clang warnings that gcc already ignores John Hubbard
2024-06-03 21:06 ` John Hubbard
2024-06-03 22:36 ` Nathan Chancellor
2024-06-07 17:23 ` Shuah Khan
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=96216e54-ba8f-4fd7-b95a-13477c143575@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=beaub@linux.microsoft.com \
--cc=broonie@kernel.org \
--cc=justinstitt@google.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=morbo@google.com \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=sunliming@kylinos.cn \
--cc=usama.anjum@collabora.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