[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06011271-65b0-4992-8d6b-8946c1c9d287@t-8ch.de>
Date: Mon, 12 Jan 2026 22:37:08 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: WangYuli <wangyuli@...c.io>
Cc: Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>, Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH] kbuild: Reject unexpected values for LLVM=
On 2026-01-12 14:58:08+0800, WangYuli wrote:
> Hi Thomas Weißschuh,
>
> On 2026/1/12 14:43, Thomas Weißschuh wrote:
>
> > The LLVM argument is documented to accept one of three forms:
> > * a literal '1' to use the default 'clang',
> > * a toolchain prefix path, ending in a trailing '/',
> > * a version suffix.
> >
> > All other values are silently treated as '1'. If for example
> > the user accidentally forgets the trailing '/' of a toolchain prefix,
> > kbuild will unexpectedly and silently fall back to the system toolchain.
> >
> > Instead report an error if the user specified an invalid value for LLVM.
> >
> "Falling back to the system toolchain" may be an acceptable behavior; I
> think reporting a warning here rather than an error would be more
> appropriate.
For which value of 'LLVM' would a silent fallback be the thing to do?
Thomas
Powered by blists - more mailing lists