[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <88887095-fd7d-4428-b96f-27e18b547b2c@arm.com>
Date: Tue, 16 Jul 2024 16:41:55 +0100
From: Leo Yan <leo.yan@....com>
To: Ian Rogers <irogers@...gle.com>, llvm@...ts.linux.dev
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling
<morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>,
James Clark <james.clark@...aro.org>, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] perf docs: Mark the Android document as obsolete
On 7/16/2024 4:05 PM, Ian Rogers wrote:
[...]
>>> I'm not sure how we detect
>>> in the build that we're using clang, I suspect there is an approach in
>>> a different kernel Makefile/Build that already tackles this but my
>>> quick searching didn't yield anything - perhaps the change would be
>>> better suited to the location the CROSS_COMPILE prefix is added to
>>> gcc.
>>
>> Should we follow up the steps in the Documentation/kbuild/llvm.rst?
>> The document uses the flag 'LLVM=1' for selecting LLVM/Clang.
>
> Fix clang-built-linux email to llvm@...ts.linux.dev
>
> I'm not sure as the kernel build and the tools build differ in certain
> ways. Perhaps look at the selftests build to see what they do, as they
> are under tools and share the build files.
Okay. thanks for suggestion.
Leo
Powered by blists - more mailing lists