From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] PowerPC64 toolchain not building
Date: Wed, 3 Feb 2016 15:45:00 +0100 [thread overview]
Message-ID: <20160203154500.4ea488e8@free-electrons.com> (raw)
In-Reply-To: <20160129005530.GA4314@tungsten.ozlabs.ibm.com>
Hello Sam,
On Fri, 29 Jan 2016 11:55:30 +1100, Sam Bobroff wrote:
> I've managed to replicate your problem!
>
> The key to reproducing it seems to be to optimise for size: I compared your
> compile line to mine, and the only difference was -Os vs. -O3 :-)
>
> So try optimizing for speed instead: this obviously works around it for me ;-)
>
> And yes, it's the lqarx instruction causing the problem: it's first argument must
> be even but it's 7, so this looks like a bug in gcc.
>
> I did some searching around and it looks like this has been a problem in the
> past and it's been fixed, but it looks like optimizing for size causes it to
> re-appear. There's a bit of related info here:
>
> http://comments.gmane.org/gmane.comp.gcc.bugs/388637
Thanks for looking into the problem.
> Would you like to raise it on https://gcc.gnu.org/bugzilla/ ?
> Alternativly, it's no problem for me handle it if you like (I work on PowerKVM
> :-).
Since you actually work on PowerPC, it would be good if you could
report the problem yourself.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-03 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:07 [Buildroot] PowerPC64 toolchain not building Thomas Petazzoni
2016-01-24 19:12 ` Waldemar Brodkorb
2016-01-24 20:36 ` Thomas Petazzoni
2016-01-27 4:38 ` Sam Bobroff
2016-01-27 8:32 ` Thomas Petazzoni
2016-01-28 2:44 ` Sam Bobroff
2016-01-28 8:17 ` Thomas Petazzoni
2016-01-28 9:20 ` Thomas Petazzoni
2016-01-29 0:55 ` Sam Bobroff
2016-02-03 14:45 ` Thomas Petazzoni [this message]
2016-01-28 9:47 ` Waldemar Brodkorb
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=20160203154500.4ea488e8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.