From: Segher Boessenkool <segher@kernel.crashing.org>
To: Cyril Bur <cyrilbur@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, akshay.adiga@linux.vnet.ibm.com
Subject: Re: [PATCH v2] powerpc: Blacklist GCC 5.4 6.1 and 6.2
Date: Mon, 13 Feb 2017 19:49:16 -0600 [thread overview]
Message-ID: <20170214014916.GR21840@gate.crashing.org> (raw)
In-Reply-To: <1487031943.9122.1.camel@gmail.com>
On Tue, Feb 14, 2017 at 11:25:43AM +1100, Cyril Bur wrote:
> > > At the time of writing GCC 5.4 is the most recent and is affected. GCC
> > > 6.3 contains the backported fix, has been tested and appears safe to
> > > use.
> >
> > 6.3 is (of course) the newer release; 5.4 is a maintenance release of
> > a compiler that is a year older.
>
> Yes. I think the point I was trying to make is that since they
> backported the fix to 5.x and 6.x then I expect that 5.5 will have the
> fix but since it doesn't exist yet, I can't be sure. I'll add something
> to that effect.
The patch has been backported to the GCC 5 branch; it will be part of
any future GCC 5 release (5.5 and later, if any later will happen; 5.5
will).
Don't be so unsure about these things, we aren't *that* incompetent ;-)
> > Please mention the GCC PR # somewhere in the code, too?
>
> Sure.
Thanks!
Segher
next prev parent reply other threads:[~2017-02-14 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 3:35 [PATCH v2] powerpc: Blacklist GCC 5.4 6.1 and 6.2 Cyril Bur
2017-02-13 15:44 ` Segher Boessenkool
2017-02-14 0:25 ` Cyril Bur
2017-02-14 1:49 ` Segher Boessenkool [this message]
2017-10-03 19:29 ` Michal Suchánek
2017-10-04 11:36 ` Michael Ellerman
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=20170214014916.GR21840@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=cyrilbur@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).