On Wed, Jul 10, 2013 at 9:57 AM, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > On Wed, Jul 10, 2013 at 9:34 AM, Enrico Scholz > <enrico.sch...@sigma-chemnitz.de> wrote: >> Enrico Scholz >> <enrico.scholz-wttK6gPy29v+Hn7q9Vec/7nah6klm...@public.gmane.org> >> writes: >> >>> is it expected that recent gcc 4.8[1] compiles the kernel correctly? >>> Kernels for ARMv5 platforms (PXA168 -> 3.4.52, MX28 -> 3.8.13) fail here >>> 100% at early boot with >> >> Applying two upstream kernel commits >> 455bd4c430b0c0a361f38e8658a0d6cb469942b5 (ARM: 7668/1: fix >> memset-related crashes caused by recent GCC (4.7.2) optimizations) and >> 418df63adac56841ef6b0f1fcf435bc64d4ed177 (ARM: 7670/1: fix the memset >> fix) seem to fix the problem for me. > > Correct. Those are the same commits you'll see on linux-yocto-3.8, we've been > soaking them for a while. I was waiting for LTSI and -stable to pick > up the changes > before updating linux-yocto-3.4, but that hasn't happened yet. > > If you are using linux-yocto-3.4 and can confirm that it boots for you > with those patches, > I can stage them in my tree while I wait for them to loop around. >
Heh. Clearly I had vacation brain when I wrote this .. I merged and pushed the two ARM gcc 4.8 fixes on June 20th, at the same time I was fixing 3.8. :) Cheers, Bruce > Cheers, > > Bruce > >> >> >> >> Enrico >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core