From: josh@joshtriplett.org
To: David Binderman <dcb314@hotmail.com>
Cc: "sparse@chrisli.org" <sparse@chrisli.org>,
"linux-sparse@vger.kernel.org" <linux-sparse@vger.kernel.org>
Subject: Re: linux-4.1-rc7 and dev versions of gcc
Date: Tue, 9 Jun 2015 08:33:42 -0700 [thread overview]
Message-ID: <20150609153341.GA2595@cloud> (raw)
In-Reply-To: <DUB128-W148850BD36B441B5C030639CBE0@phx.gbl>
On Tue, Jun 09, 2015 at 07:35:58AM +0000, David Binderman wrote:
> Hello there,
>
> Recent development versions of gcc have started using the 6.0.0 version number.
>
> gcc version 6.0.0 20150607 (experimental) (GCC)
>
> Linux kernel doesn't understand any gcc version numbers beyond 5.
>
> include/linux/compiler-gcc3.h
> include/linux/compiler-gcc4.h
> include/linux/compiler-gcc5.h
>
> Kernel build fails because no compiler-gcc6.h file.
>
> I have a temporary bodge to copy compiler-gcc5.h file into compiler-gcc6.h
This shouldn't be a Sparse issue. As discussed previously on this list
and LKML, Sparse should probably declare a specific GCC version number,
*not* the latest. Apart from that, handling GCC 6 has been discussed on
LKML previously, and I think there were some patches circulating
already.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-06-09 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 7:35 linux-4.1-rc7 and dev versions of gcc David Binderman
2015-06-09 15:33 ` josh [this message]
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=20150609153341.GA2595@cloud \
--to=josh@joshtriplett.org \
--cc=dcb314@hotmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.