From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Arnd Bergmann <arnd@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Android Kernel Team <kernel-team@android.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64
Date: Wed, 13 Jan 2021 15:02:32 +0000 [thread overview]
Message-ID: <20210113150232.GA27045@gaia> (raw)
In-Reply-To: <CAHk-=wh-+TMHPTFo1qs-MYyK7tZh-OQovA=pP3=e06aCVp6_kA@mail.gmail.com>
On Tue, Jan 12, 2021 at 06:35:50PM -0800, Linus Torvalds wrote:
> On Tue, Jan 12, 2021 at 6:14 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Ack. I'll assume I get this the usual ways from the arm64 tree..
>
> Oh.. Actually, while you can use my ack if you decide to go this way,
> I do wonder if it might not be better to introduce a notion of an
> error at Kconfig time, and then we could make this whole GCC_VERSION
> check be something that gets covered much earlier - when configuring
> the kernel, rather than randomly (ok, very early) when building it.
>
> We already have the CONFIG_GCC_VERSION config variable, after all.
>
> And Kconfig already has an error functionality, which it uses for
> things like compilers not found etc.
>
> So something like
>
> $(error-if,CC_IS_GCC && GCC_VERSION < 90100,"Gcc version too old")
>
> in the arm64 Kconfig file should do it.
$(error-if) seems to expect a y/n as a condition. We do have $(failure)
and $(success) but they translate a (shell) command's return code to
y/n. Even with something like:
config GCC_IS_OLD
def_bool CC_IS_GCC && GCC_VERSION < ...
I can't get $(error-if,GCC_IS_OLD) to expand the config value, no matter
what other. GCC_VERSION is also a config option in your example.
I'll queue Will's patch in the meantime.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-13 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:48 [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 Will Deacon
2021-01-12 22:57 ` Nick Desaulniers
2021-01-12 23:06 ` Nathan Chancellor
2021-01-13 2:14 ` Linus Torvalds
2021-01-13 2:35 ` Linus Torvalds
2021-01-13 15:02 ` Catalin Marinas [this message]
2021-01-13 16:07 ` Catalin Marinas
2021-01-13 17:57 ` Masahiro Yamada
2021-01-13 18:33 ` Joe Perches
2021-01-13 19:15 ` Linus Torvalds
2021-01-13 21:44 ` Russell King - ARM Linux admin
2021-01-13 22:08 ` Linus Torvalds
2021-01-14 8:18 ` Ard Biesheuvel
2021-01-14 18:43 ` Linus Torvalds
2021-01-14 19:51 ` Joe Perches
2021-01-14 21:18 ` Linus Torvalds
2021-01-15 0:30 ` Joe Perches
2021-01-15 23:24 ` Linus Torvalds
2021-02-27 7:16 ` 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=20210113150232.GA27045@gaia \
--to=catalin.marinas@arm.com \
--cc=arnd@kernel.org \
--cc=fweimer@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).