On Wed, 2013-08-14 at 14:18 +1000, Benjamin Herrenschmidt wrote: > On Thu, 2013-08-08 at 17:45 -0500, Scott Wood wrote: > > powerpc/e500: Update compilation flags with core specific > > options > > This breaks the build for my FSL test configs. For some reason gcc 4.7.3 > doesn't know about -mcpu=e5500
Ugh. I guess that's what I get for using toolchains provided internally rather than building them myself -- though it doesn't help that the GCC people love finding new ways to break building GCC without libc (why doesn't --without-headers automatically disable any component that requires libc headers?), and usually respond to bug reports with "go run crosstool and leave us alone". It looks like e5500 support is in 4.8.1, but I can't actually get it to build (libdecnumber wants to #include_next <stdlib.h> and can't be disabled -- arm64 toolchain built fine with the similar configure options). I don't know about earlier versions. > Additionally, on 64-bit, that means one can no longer make a kernel that > does both A2 and e5500... Other than the toolchain issue, I'm not sure how this is worse than it was before, when such a kernel would have had -Wa,-me500 forced. What -mcpu value should be used in such a combined kernel? > I'm reverting that crap patch, please make such optimizations CONFIG_* > options like power5...7 Speaking of crap patches, those config options don't limit themselves to book3s and thus we're now getting CONFIG_GENERIC_CPU (and thus -mtune=power7) on e5500 builds. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
