Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Bur <cyrilbur@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: Add GCC 5.2.x option
Date: Mon, 29 Feb 2016 09:22:37 +1100	[thread overview]
Message-ID: <20160229092237.33dabe93@camb691> (raw)
In-Reply-To: <20160226093720.7fcd4e10@free-electrons.com>

On Fri, 26 Feb 2016 09:37:20 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Cyril,
> 
> On Fri, 26 Feb 2016 14:15:48 +1100, Cyril Bur wrote:
> > GCC 5.3.x introduces a regression with PowerPC Altivec/VSX code generation.
> > 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69969
> > 
> > Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> > ---
> > I'm not sure if this patch is worth the trouble. By the looks of it the GCC
> > guys are aiming to have a fix in 5.4 and it is unlikely most users are
> > doing things that would result in them hitting the bug.  
> 
> Like we did for previous gcc versions, we only want to support one
> minor version at a time for a given major branch.
> 
> So at the gcc 4 era, it meant we would only package one gcc 4.8, one
> gcc 4.9, etc.
> 
> At the gcc >= 5 era, it means we want to package only one 5.x version,
> one 6.x version, etc.
> 
> If you want to fix the problem without waiting for gcc 5.4, what I can
> suggest is to backport the fixes for the regression you are
> experiencing.

No fix exists yet but yeah upstreaming this patch is definitely more headache
in the long run, I just thought I'd put it out here - it's probably the easiest
fix to this problem (for now) so in the unlikely event that anyone else hits
it, hopefully they'll find this.


Thanks for the response,

Cyril

> 
> Thomas

      reply	other threads:[~2016-02-28 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  3:15 [Buildroot] [PATCH] gcc: Add GCC 5.2.x option Cyril Bur
2016-02-26  8:37 ` Thomas Petazzoni
2016-02-28 22:22   ` 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=20160229092237.33dabe93@camb691 \
    --to=cyrilbur@gmail.com \
    --cc=buildroot@busybox.net \
    /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