From: Nick Desaulniers <ndesaulniers@google.com>
To: joe@perches.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
dave.hansen@intel.com, efault@gmx.de,
Guenter Roeck <linux@roeck-us.net>,
riel@surriel.com, Kees Cook <keescook@chromium.org>,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Raise the minimum required gcc version to 4.6
Date: Mon, 20 Aug 2018 13:25:28 -0700 [thread overview]
Message-ID: <CAKwvOdmaABwZhZ0YCPBhuiq+hMrSF=Ad_sOD04d8+ab5QLLXhA@mail.gmail.com> (raw)
In-Reply-To: <da5620dc7a2b9d33f2a0dd7f4dc3afdab5a66f26.1534795606.git.joe@perches.com>
On Mon, Aug 20, 2018 at 1:15 PM Joe Perches <joe@perches.com> wrote:
>
> Various architectures fail to build properly with older versions
> of the gcc compiler.
Just curious if certain arch's require older versions of gcc? Surely
that's not the case, but hopefully this patch wont surprise anyone.
It might be worthwhile to see where else in the kernel has
/gcc\s+[0-9]/g as I'm sure there's other old-gcc workarounds that can
go too (in follow up patches).
Thanks for sending. This helps us ship newer compiler features for
which older compiler support is difficult/impossible.
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2018-08-20 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 20:15 [PATCH] Raise the minimum required gcc version to 4.6 Joe Perches
2018-08-20 20:25 ` Nick Desaulniers [this message]
2018-08-20 20:42 ` Jonathan Corbet
2018-08-20 20:48 ` Joe Perches
2018-08-21 6:55 ` Masahiro Yamada
2018-08-21 19:40 ` Linus Torvalds
2018-08-21 23:41 ` Nick Desaulniers
2018-08-23 21:52 ` Geert Uytterhoeven
2018-08-23 22:00 ` Nick Desaulniers
2018-08-23 22:00 ` Joe Perches
2018-12-29 14:25 ` Geert Uytterhoeven
2018-12-29 21:57 ` Arnd Bergmann
2019-01-08 14:09 ` Geert Uytterhoeven
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='CAKwvOdmaABwZhZ0YCPBhuiq+hMrSF=Ad_sOD04d8+ab5QLLXhA@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=riel@surriel.com \
--cc=torvalds@linux-foundation.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).