Gcc uses the same -march= for both -m32 and -m64 on x86-64 unless --with-arch-32= is used. There is no need for -march=i486 to compile 32-bit libgomp on x86-64.
Tested on x86-64. OK for trunk? H.J. --- PR target/70454 * configure.tgt (XCFLAGS): Don't add -march=i486 to compile 32-bit target library on x86-64. --- libgomp/configure.tgt | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/libgomp/configure.tgt b/libgomp/configure.tgt index 77e73f0..a36acc5 100644 --- a/libgomp/configure.tgt +++ b/libgomp/configure.tgt @@ -79,16 +79,10 @@ if test x$enable_linux_futex = xyes; then esac ;; - # Similar jiggery-pokery for x86_64 multilibs, except here we - # can't rely on the --with-arch configure option, since that - # applies to the 64-bit side. x86_64-*-linux*) config_path="linux/x86 linux posix" - case " ${CC} ${CFLAGS} " in - *" -m32 "*) - XCFLAGS="${XCFLAGS} -march=i486 -mtune=generic" - ;; - esac + # Since 64-bit arch > i486, we can use the same -march= to build + # both 32-bit and 64-bit target libraries. ;; # Note that sparcv7 and sparcv8 is not included here. We need cas. -- 2.5.5