<br><br>On Wednesday, August 13, 2014, Otavio Salvador &lt;<a href="mailto:otavio@ossystems.com.br">otavio@ossystems.com.br</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Aug 13, 2014 at 6:24 PM, Gary Thomas &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;gary@mlbassoc.com&#39;)">gary@mlbassoc.com</a>&gt; wrote:<br>
&gt; I&#39;ve found that the latest GCC doesn&#39;t work very well, at<br>
&gt; least not on ARM (and obviously other architectures as well [1])<br>
&gt; When I build Google Chromium browser for my i.MX boards using<br>
&gt; GCC-4.9.x, no pages can be rendered - massive bloodshed and<br>
&gt; failures are shown on the console.  If I use the older GCC 4.8.2,<br>
&gt; everything else the same, all is well.<br>
&gt;<br>
&gt; Here&#39;s my configuration:<br>
&gt; BB_VERSION        = &quot;1.23.1&quot;<br>
&gt; BUILD_SYS         = &quot;x86_64-linux&quot;<br>
&gt; NATIVELSBSTRING   = &quot;Ubuntu-13.10&quot;<br>
&gt; TARGET_SYS        = &quot;arm-amltd-linux-gnueabi&quot;<br>
&gt; MACHINE           = &quot;teton-p0382&quot;<br>
&gt; DISTRO            = &quot;amltd&quot;<br>
&gt; DISTRO_VERSION    = &quot;1.6+snapshot-20140812&quot;<br>
&gt; TUNE_FEATURES     = &quot;arm armv7a vfp neon callconvention-hard cortexa9&quot;<br>
&gt; TARGET_FPU        = &quot;vfp-neon&quot;<br>
&gt; meta              = &quot;master:86afd7eb7c679eb065706137f28f44248f3fbc5a&quot;<br>
&gt; meta-amltd        = &quot;master:899529b4184dc9e3e291e7fcdbbf157233db056d&quot;<br>
&gt; meta-teton-imx6-p0382 = &quot;master:9188e2f8fafd203c95dcd7a3c79cb38a1568e9b5&quot;<br>
&gt; meta-fsl-arm      = &quot;master:b0cf5c78c5f98c5977ae556d331e7495648f154c&quot;<br>
&gt; meta-fsl-arm-extra = &quot;master:12e560967b7136222c325d11633295fe3a0c701c&quot;<br>
&gt; meta-browser      = &quot;master:da93c8e386133a15eff1414d9307c8f2c7a44787&quot;<br>
&gt;<br>
&gt; Should this be filed as a bug?  I don&#39;t have much data other than it<br>
&gt; simply breaks (and chrome is not the easiest thing to debug!).  Other<br>
&gt; applications seem OK, but I am loathe to trust it...<br>
&gt;<br>
&gt; I&#39;m going to hold onto GCC-4.8.x for my $DISTRO at least (and I hope<br>
&gt; it doesn&#39;t vanish like 4.7.x did too quickly).<br>
&gt;<br>
&gt; [1]<br>
&gt; <a href="http://slashdot.org/story/14/07/27/1838219/linus-torvalds-gcc-490-seems-to-be-terminally-broken" target="_blank">http://slashdot.org/story/14/07/27/1838219/linus-torvalds-gcc-490-seems-to-be-terminally-broken</a><br>

&gt;<br>
&gt; Note: I&#39;ve also tried this on qemux86 (a totally different<br>
&gt; architecture) and chrome bombs just as badly!<br>
<br>
I confirm that GCC 4.9 does NOT work for Chromium 35. At this moment I<br>
am not aware of any fix for it.</blockquote><div><br></div><div>Again Its a broad brush statement. Something concrete is needed if some.action is to taken</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
IIRC the Chromium 37 works though.<br>
<br></blockquote><div><br></div><div>Well then its less chance.that someone will fix 35 </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
--<br>
Otavio Salvador                             O.S. Systems<br>
<a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a>        <a href="http://code.ossystems.com.br" target="_blank">http://code.ossystems.com.br</a><br>
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750<br>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Openembedded-core@lists.openembedded.org&#39;)">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote>