On 8/6/2021 8:42 PM, Thomas Gleixner wrote:

On Wed, Aug 04 2021 at 17:04, Rong A. Chen wrote:

quoted

On 7/27/2021 10:52 PM, Dave Hansen wrote:

quoted

On 7/26/21 8:11 PM, kernel test robot wrote:

quoted

quoted

quoted

sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'

Is there something else funky going on here?  All of the "-mxsave" flags
that I can find are under checks for x86 builds, like:

	ifeq ($(CAN_BUILD_I386),1)
	$(BINARIES_32): CFLAGS += -m32 -mxsave
	..

I'm confused how we could have a sparc64 compiler (and only a sparc64
compiler) that would end up with "-mxsave" in CFLAGS.

Hi Dave,

We can reproduce the error and have no idea too, but we have disabled
the test for selftests on non-x86 arch.

This smells like a host/target compiler mixup. Can you please make the
kernel build verbose with 'V=1' and provide the full build output?

Hi Thomas,

I run the below command:

$make V=1 --keep-going CROSS_COMPILE=sparc64-linux- -j1 O=build_dir 
ARCH=sparc64 -C tools/testing/selftests/vm
...
sparc64-linux-gcc -Wall -I ../../../../usr/include  -no-pie -m32 -mxsave 
  protection_keys.c -lrt -lpthread -lrt -ldl -lm -o 
/root/linux/tools/testing/selftests/vm/protection_keys_32
sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
make: *** [Makefile:107: 
/root/linux/tools/testing/selftests/vm/protection_keys_32] Error 1
sparc64-linux-gcc -Wall -I ../../../../usr/include  -no-pie -m64 -mxsave 
  protection_keys.c -lrt -lpthread -lrt -ldl -o 
/root/linux/tools/testing/selftests/vm/protection_keys_64
sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
make: *** [Makefile:115: 
/root/linux/tools/testing/selftests/vm/protection_keys_64] Error 1

and I attached the full build output for your reference.

Best Regards,
Rong Chen