buildgcc: Never set GMP CFLAGS manually in order to get the right flags
When no CFLAGS are explicitly provided to it, the GMP configure script will figure out the best optimization flags to use on its own. In particular, it will setup the march, mfpu and mtune flags based on hardware detection. However, when CFLAGS are provided, they are used as-is and such detection doesn't happen. When the march, mfpu and mtune flags are not provided (which happens when GMP wasn't built already), not only will related optimizations be disabled, but some code might not build because of missing support. This happens with NEON instructions on ARMv7 hosts. Thus, it is better not to set CFLAGS and leave it up to the GMP configure script to get them right and still reuse those later. Change-Id: I6ffcbac1298523d1b8ddf29a8bca1b00298828a7 Signed-off-by: Paul Kocialkowski <contact@paulk.fr> Reviewed-on: https://review.coreboot.org/15452 Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Tested-by: build bot (Jenkins) Reviewed-by: Nico Huber <nico.h@gmx.de>
This commit is contained in:
parent
67870f508f
commit
7899db2355
|
@ -440,8 +440,7 @@ set_hostcflags_from_gmp() {
|
||||||
}
|
}
|
||||||
|
|
||||||
build_GMP() {
|
build_GMP() {
|
||||||
CC="$CC" CFLAGS="$HOSTCFLAGS" \
|
CC="$CC" ../${GMP_DIR}/configure --disable-shared --enable-fat \
|
||||||
../${GMP_DIR}/configure --disable-shared --enable-fat \
|
|
||||||
--prefix=$TARGETDIR $OPTIONS \
|
--prefix=$TARGETDIR $OPTIONS \
|
||||||
|| touch .failed
|
|| touch .failed
|
||||||
$MAKE $JOBS || touch .failed
|
$MAKE $JOBS || touch .failed
|
||||||
|
|
Loading…
Reference in New Issue