On Sat, Feb 6, 2021 at 12:46 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:
>
> On Sat, Feb 6, 2021 at 2:49 AM Masahiro Yamada <masahiroy@xxxxxxxxxx> wrote:
> >
> > On Sat, Feb 6, 2021 at 7:01 AM 'Nick Desaulniers' via Clang Built
> > Linux <clang-built-linux@xxxxxxxxxxxxxxxx> wrote:
> > >
> > > I noticed we're invoking $(CC) via $(shell) more than once to check the
> > > version. Let's reuse the first string captured in $CC_VERSION_TEXT.
> > >
> > > Fixes: 315bab4e972d ("kbuild: fix endless syncconfig in case arch Makefile sets CROSS_COMPILE")
> >
> >
> > I did not touch this hunk because I have a plan
> > for different refactoring, but I have never got
> > around to do it.
> >
> > Anyway, you beat me, and I will pick this up.
> > But, the Fixes tag is questionable because
> > this is code refactoring.
> >
>
> When I see this... and hear refactoring... As a suggestion/improvement...
>
> Can we have LD_VERSION_TEXT analogue to CC_VERSION_TEXT?
> Both are shown when doing a `cat /proc/version` (and IIRC in file
> include/generated/compile.h).
Sorry, I had forgotten to answer this question.
Probably, we should do so.
Feeding it to Kconfig allows us to re-evaluate
config settings when tools are upgraded.
One question is where we should draw a line.
If we record the version text of CC, LD,
we should do that for more tools?
For LD, I will be probably OK because
some features rely on LD_VERSION or $(ld-option ).
--
Best Regards
Masahiro Yamada
