Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: GCC 4.9 considered evil
Date: Wed, 13 Aug 2014 15:24:16 -0600	[thread overview]
Message-ID: <53EBD780.9060005@mlbassoc.com> (raw)

I've found that the latest GCC doesn't work very well, at
least not on ARM (and obviously other architectures as well [1])
When I build Google Chromium browser for my i.MX boards using
GCC-4.9.x, no pages can be rendered - massive bloodshed and
failures are shown on the console.  If I use the older GCC 4.8.2,
everything else the same, all is well.

Here's my configuration:
BB_VERSION        = "1.23.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-13.10"
TARGET_SYS        = "arm-amltd-linux-gnueabi"
MACHINE           = "teton-p0382"
DISTRO            = "amltd"
DISTRO_VERSION    = "1.6+snapshot-20140812"
TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU        = "vfp-neon"
meta              = "master:86afd7eb7c679eb065706137f28f44248f3fbc5a"
meta-amltd        = "master:899529b4184dc9e3e291e7fcdbbf157233db056d"
meta-teton-imx6-p0382 = "master:9188e2f8fafd203c95dcd7a3c79cb38a1568e9b5"
meta-fsl-arm      = "master:b0cf5c78c5f98c5977ae556d331e7495648f154c"
meta-fsl-arm-extra = "master:12e560967b7136222c325d11633295fe3a0c701c"
meta-browser      = "master:da93c8e386133a15eff1414d9307c8f2c7a44787"

Should this be filed as a bug?  I don't have much data other than it
simply breaks (and chrome is not the easiest thing to debug!).  Other
applications seem OK, but I am loathe to trust it...

I'm going to hold onto GCC-4.8.x for my $DISTRO at least (and I hope
it doesn't vanish like 4.7.x did too quickly).

[1] http://slashdot.org/story/14/07/27/1838219/linus-torvalds-gcc-490-seems-to-be-terminally-broken

Note: I've also tried this on qemux86 (a totally different
architecture) and chrome bombs just as badly!

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2014-08-13 21:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 21:24 Gary Thomas [this message]
2014-08-13 22:54 ` GCC 4.9 considered evil Khem Raj
2014-08-13 23:25 ` Otavio Salvador
2014-08-14  0:46   ` Khem Raj
2014-08-14  8:12     ` Carlos Rafael Giani
2014-08-14  8:22       ` Peter A. Bigot
2014-08-14  8:24         ` Carlos Rafael Giani
2014-08-14 10:02           ` Peter A. Bigot
2014-08-14 10:44             ` Gary Thomas
2014-08-15 14:53           ` Martin Jansa
2014-08-14 18:14         ` Carlos Rafael Giani
2014-08-14 19:11           ` Peter A. Bigot

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=53EBD780.9060005@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.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