[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable-smoke test] 130708: regressions - trouble: blocked/broken/fail/pass

>>> On 23.11.18 at 07:20, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> flight 130708 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/130708/ 
> Regressions :-(
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-arm64-xsm                 <job status>                 broken
>  build-amd64                   6 xen-build                fail REGR. vs. 
> 130289

I'm puzzled: The "all" target of tools/tests/x86_emulator/Makefile
reliably does nothing for me with 05f4cc2192, yet it looks to not
work here:

make -C x86_emulator all
make[5]: Entering directory 
[ -L x86_emulate ] || ln -sf 
gcc  -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wdeclaration-after-statement -Wno-unused-but-set-variable 
-Wno-unused-local-typedefs   -g3 -O0 -fno-omit-frame-pointer 
-c -o cpuid.o 
rm -f blowfish.h.new blowfish.bin
ln -sf simd.c 3dnow.c
ln -sf simd.c sse.c

Would one of you be in the position (and have the time) to determine
why the detection logic added by the commit does not work there?
What I'm seeing here (but not in the osstest build log) ahead of the
make warning the commit adds is a bunch of

cc1: error: unrecognized command line option "-mavx"

and alike (which I've intentionally not redirected into /dev/null).
Hence I wonder whether either the make version or the gcc version
used there differ in behavior from the ones I've been testing with.
The odd thing is that later on in the build log such compiler errors
do show up:

gcc: error: unrecognized command line option '-mavx512dq'


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.