From: Cyril Bur <cyrilbur@gmail.com>
To: Christophe LEROY <christophe.leroy@c-s.fr>,
linuxppc-dev@lists.ozlabs.org
Cc: akshay.adiga@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc: Blacklist GCC 5.4 6.1 and 6.2
Date: Mon, 13 Feb 2017 11:23:28 +1100 [thread overview]
Message-ID: <1486945408.2733.1.camel@gmail.com> (raw)
In-Reply-To: <6f4d7111-6747-db55-c2c0-10aefa009f6d@c-s.fr>
On Fri, 2017-02-10 at 08:48 +0100, Christophe LEROY wrote:
>
> Le 10/02/2017 à 06:31, Cyril Bur a écrit :
> > A bug in the -02 optimisation of GCC 5.4 6.1 and 6.2 causes
> > setup_command_line() to not pass the correct first argument to strcpy
> > and therefore not actually copy the command_line.
> >
> > A workaround patch was proposed: http://patchwork.ozlabs.org/patch/673130/
> > some discussion ensued.
> >
> > A GCC bug was raised: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709
> > The bug has been fixed in 7.0 and backported to GCC 5 and GCC 6.
> >
> > 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.
> >
> > Heavy-lifting-by: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
> > Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> > ---
> > arch/powerpc/Makefile | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> > index 31286fa7873c..a4b886694391 100644
> > --- a/arch/powerpc/Makefile
> > +++ b/arch/powerpc/Makefile
> > @@ -414,6 +414,15 @@ checkbin:
> > echo -n '*** Please use a different binutils version.' ; \
> > false ; \
> > fi
> > + @if test "$(cc-version)" = "0504" \
> > + || test "$(cc-version)" = "0601" \
> > + || test "$(cc-version)" = "0602" ; then \
> > + echo -n '*** GCC-5.4 6.1 6.2 have a bad -O2 optimisation ' ; \
> > + echo 'which will cause lost commandline options (at least).' ; \
> > + echo '*** Please use a different GCC version.' ; \
> > + false ; \
> > + fi
> > +
>
> According to the GCC bug report, this bug applies to powerpc64le
> Why force all targets to not use those versions of GCC ?
>
True, I'll double check on BE, these days BE does suffer from, "oops I
didn't check that". If it is only LE, I'll add another condition.
Thanks,
Cyril
> Christophe
prev parent reply other threads:[~2017-02-13 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 5:31 [PATCH] powerpc: Blacklist GCC 5.4 6.1 and 6.2 Cyril Bur
2017-02-10 7:48 ` Christophe LEROY
2017-02-13 0:23 ` Cyril Bur [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=1486945408.2733.1.camel@gmail.com \
--to=cyrilbur@gmail.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=christophe.leroy@c-s.fr \
--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 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.