On Sun, Mar 4, 2018 at 8:22 AM, Martin Jansa <[email protected]> wrote: > On Sun, Mar 04, 2018 at 03:15:38PM +0100, Martin Jansa wrote: >> On Sun, Mar 04, 2018 at 11:21:32AM +0000, Richard Purdie wrote: >> > From: Juro Bystricky <[email protected]> >> > >> > Changed BINV and PV from 6.2.0 to 6.4.0 >> > Modified BASEURI to load xz tarball instead of bz2 >> > >> > Backported series of patches from https://github.com/hjl-tools/gcc.git >> > branch /hjl/indirect/gcc-6-branch/master which contains >> > an IA patch series for security related issues >> > >> > ubsan-fix-check-empty-string.patch : removed, already applied >> >> Very limited testing with this change in morty shows that raspberrypi3 >> (cortexa7hf-neon-vfpv4) build of glibc-initial fails with: >> >> configure:5344: checking for broken __attribute__((alias())) >> configure:5359: arm-oe-linux-gnueabi-gcc -march=armv7ve -marm >> -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 >> --sysroot=sysroots/raspberrypi3-tcbootstrap >> -Werror -S conftest.c -o conftest.s 1>&5 >> conftest.c:1:0: error: switch -mcpu=cortex-a7 conflicts with >> -march=armv7ve switch [-Werror] >> extern int foo (int x) __asm ("xyzzy"); >> >> cc1: all warnings being treated as errors >> configure:5362: $? = 1 >> configure:5372: result: yes >> configure:5375: error: working alias attribute support required >> >> Which is a bit strange as armv7ve was added to resolve this error with >> -mcpu=cortexa7 and -march=armv7a in: >> >> commit 35392025f3236f5e5393f9cf0857732da9a2e503 >> Author: Martin Jansa <[email protected]> >> Date: Tue Oct 6 17:08:59 2015 +0200 >> >> arch-armv7ve: add tune include for armv7ve and use it from cortexa7 >> and cortexa15 >> >> * be aware that this -march value is available only in gcc-4.9 and >> newer: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57907 >> * -mcpu=cortex15 and -mcpu=cortexa7 conflict with -march=armv7a >> We either have to stop putting -march in default CCARGS or at >> least set it compatible one like this patch does. >> >> Regards, > > It seems to be known regression in 6.4, with fix available here: > https://patchwork.ozlabs.org/patch/835592/
Yes. Not only was the patch submitted upstream to gcc, it was even submitted to oe-core: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144159.html Unfortunately gcc 6.4.0 was dropped from oe-core master before the fix was merged... -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
