#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org
#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org
-----------------------------+------------------------
Reporter: jakub | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
In the gcc-4.9.0-12.fc21 build logs I saw a weird error:
/builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/xgcc
-B/builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/
/builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -march=native
-lm -o ./pr57275.exe
/builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c:1:0:
error: CPU you selected does not support x86-64 instruction set
and I'd like to debug that, but don't know of a way to force e.g. a
scratch rpm build to a particular build host. Would it be possible for
some release engineer to run
gcc -v -march=native -S -xc /dev/null -o /tmp/foo.s
cat /proc/cpuinfo
in the F21 mock chroot on that box? Perhaps we are missing something in
the -m{arch,tune}=native logic,
a CPU which clearly does support x86_64 64-bit ISA should not be
determined as one that does not.
Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5924>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project