From: Matthew Wilcox <willy@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2] kbuild: Make $(LLVM) more flexible
Date: Tue, 8 Mar 2022 16:36:17 +0000 [thread overview]
Message-ID: <YieGARVP2dhn8tbQ@casper.infradead.org> (raw)
In-Reply-To: <CAKwvOd=Q-7vPaRPj1wQagFsY3txcAKzrqU_D2UAX3h4ym91uUA@mail.gmail.com>
On Mon, Mar 07, 2022 at 11:08:29AM -0800, Nick Desaulniers wrote:
> > +``LLVM=0`` is not the same as omitting ``LLVM`` altogether, it will behave like
> > +``LLVM=1``.
>
> Hmm... I can see someone's build wrappers setting LLVM=1, then them
> being surprised that appending LLVM=0 doesn't disable LLVM=1 as they
> might expect. But Masahiro says let's fix this later which is fine.
What happens if you say LLVM= instead of LLVM=0 ? Would that "undo"
a prior LLVM=1 and use GCC instead?
next prev parent reply other threads:[~2022-03-08 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 17:08 [PATCH v2] kbuild: Make $(LLVM) more flexible Nathan Chancellor
2022-03-04 18:09 ` Kees Cook
2022-03-04 18:15 ` Nathan Chancellor
2022-03-04 18:55 ` Masahiro Yamada
2022-03-07 19:08 ` Nick Desaulniers
2022-03-08 15:47 ` Nathan Chancellor
2022-03-09 9:33 ` Masahiro Yamada
2022-03-10 17:36 ` Nathan Chancellor
2022-03-18 5:16 ` Masahiro Yamada
2022-03-10 0:36 ` Nick Desaulniers
2022-03-08 16:36 ` Matthew Wilcox [this message]
2022-03-09 9:29 ` Masahiro Yamada
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=YieGARVP2dhn8tbQ@casper.infradead.org \
--to=willy@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--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