From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
Sasha Levin <sasha.levin@oracle.com>
Cc: akpm@linuxfoundation.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: add support for gcc 5
Date: Fri, 05 Sep 2014 00:43:48 +0200 [thread overview]
Message-ID: <1409870628.2310799.163815377.623F33D2@webmail.messagingengine.com> (raw)
In-Reply-To: <20140904212535.GA5059@drone.musicnaut.iki.fi>
Hello,
On Thu, Sep 4, 2014, at 23:25, Aaro Koskinen wrote:
> On Thu, Sep 04, 2014 at 11:37:19AM -0400, Sasha Levin wrote:
> > We're missing include/linux/compiler-gcc5.h which is required now
> > because gcc branched off to v5 in trunk.
> >
> > Just copy the relevant bits out of include/linux/compiler-gcc4.h,
> > no new code is added as of now.
> >
> > This fixes a build error when using gcc 5.
>
> With the new GCC version numbering scheme, does this mean there will
> be a new such file to be added every year? Maybe this could be handled
> some other way?
I agree, with the new gcc roadmap announced back in August [1] they tend
to increase the major number with each yearly release. I don't think it
is feasable to add a new header every year in a timely manner.
Most statements are already depending on GCC_VERSION, maybe we can just
unify all gcc specific headers to one, still trying to keep the file
organized? ;)
[1] https://gcc.gnu.org/develop.html (Section "Version Numbering Scheme
for GCC 5 and Up")
Bye,
Hannes
next prev parent reply other threads:[~2014-09-04 22:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 15:37 Sasha Levin
2014-09-04 21:12 ` Andrew Morton
2014-09-04 21:19 ` Richard Weinberger
2014-09-04 21:25 ` Andrew Morton
2014-09-04 21:38 ` Sasha Levin
2014-09-05 15:04 ` H. Peter Anvin
2014-09-04 21:25 ` Aaro Koskinen
2014-09-04 21:32 ` Sasha Levin
2014-09-04 22:43 ` Hannes Frederic Sowa [this message]
2014-09-04 23:47 ` Joe Perches
2014-09-05 3:37 ` Sasha Levin
2014-09-05 3:58 ` Joe Perches
2014-09-05 4:08 ` Hannes Frederic Sowa
2014-09-05 14:44 ` Sasha Levin
2014-09-05 20:39 ` [PATCH] gcc: clamp gcc version to most highest specific header version available Hannes Frederic Sowa
2014-09-05 21:09 ` Joe Perches
2014-09-05 22:38 ` Hannes Frederic Sowa
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=1409870628.2310799.163815377.623F33D2@webmail.messagingengine.com \
--to=hannes@stressinduktion.org \
--cc=aaro.koskinen@iki.fi \
--cc=akpm@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
/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
all inboxes | Powered by JetHome®