From: Joe Perches <joe@perches.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Miguel Ojeda <ojeda@kernel.org>,
Paul Mackerras <paulus@samba.org>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sun, 02 May 2021 13:00:28 -0700 [thread overview]
Message-ID: <81a926a3bdb70debe3ae2b13655ea8d249fb9991.camel@perches.com> (raw)
In-Reply-To: <20210502183030.GF10366@gate.crashing.org>
On Sun, 2021-05-02 at 13:30 -0500, Segher Boessenkool wrote:
> On Sat, May 01, 2021 at 07:41:53PM -0700, Joe Perches wrote:
> > Why not raise the minimum gcc compiler version even higher?
On Sun, 2021-05-02 at 13:37 -0500, Segher Boessenkool wrote:
> Everyone should always use an as new release as practical
[]
> The latest GCC 5 release is only three and a half years old.
You argue slightly against yourself here.
Yes, it's mostly a question of practicality vs latest.
clang requires a _very_ recent version.
gcc _could_ require a later version.
Perhaps 8 might be best as that has a __diag warning control mechanism.
gcc 8.1 is now 3 years old today.
_______________________________________________
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-05-02 20:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 17:38 ` Christophe Leroy
2021-05-02 2:41 ` Joe Perches
2021-05-02 18:30 ` Segher Boessenkool
2021-05-02 20:00 ` Joe Perches [this message]
2021-05-02 20:32 ` Segher Boessenkool
2021-05-02 21:05 ` Ali Kaasinen
2021-05-02 21:08 ` Linus Torvalds
2021-05-02 22:30 ` Matthew Wilcox
2021-05-03 7:34 ` Alexander Dahl
2021-05-03 8:54 ` Joe Perches
2021-05-03 9:25 ` Arnd Bergmann
2021-05-03 12:20 ` David Laight
2021-05-03 13:10 ` Miguel Ojeda
2021-05-04 5:30 ` Alexander Dahl
2021-05-04 6:33 ` Christophe Leroy
2021-05-04 12:07 ` Arnd Bergmann
2021-05-04 13:25 ` Andy Shevchenko
2021-05-03 11:35 ` Arnd Bergmann
2021-05-03 9:49 ` Kirill A. Shutemov
2021-05-02 21:23 ` Joe Perches
2021-05-03 0:44 ` Segher Boessenkool
2021-05-03 9:57 ` Arnd Bergmann
2021-05-04 7:56 ` Ben Dooks
2021-05-04 8:38 ` Miguel Ojeda
2021-05-04 9:22 ` Michal Suchánek
2021-05-04 12:09 ` Miguel Ojeda
2021-05-04 12:17 ` Michal Suchánek
2021-05-04 12:26 ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-03 6:16 ` Christophe Leroy
2021-05-04 2:13 ` Masahiro Yamada
2021-05-04 13:18 ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-15 7:14 ` Pavel Machek
2021-05-15 7:27 ` Joe Perches
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=81a926a3bdb70debe3ae2b13655ea8d249fb9991.camel@perches.com \
--to=joe@perches.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.org \
--cc=torvalds@linux-foundation.org \
--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).