From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Florian Weimer <fweimer@redhat.com>,
Arnd Bergmann <arnd@kernel.org>,
"Cc: Android Kernel" <kernel-team@android.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64
Date: Thu, 14 Jan 2021 13:18:53 -0800 [thread overview]
Message-ID: <CAHk-=wjgvt1Ei72BTrEH5fgfqykVH-AYt56-7yBT8Lcprj7bEg@mail.gmail.com> (raw)
In-Reply-To: <fd3f26b7a70d3b90f1368c55532e463ef2fb9fa4.camel@perches.com>
On Thu, Jan 14, 2021 at 11:52 AM Joe Perches <joe@perches.com> wrote:
>
> Given the upgrade requirement, and how clang version requirements
> constantly change, how much more difficult would it be for others
> to use gcc 7.1 or higher now instead of later?
What was the argument for jumping all the way to gcc-7.1?
I do think we want to have real reasons we can point to, rather than a
"just because".
Linus
next prev parent reply other threads:[~2021-01-14 21:20 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
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 [this message]
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='CAHk-=wjgvt1Ei72BTrEH5fgfqykVH-AYt56-7yBT8Lcprj7bEg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fweimer@redhat.com \
--cc=joe@perches.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=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).