Mailing List Archive

sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ff1176468d368232b684f75e82563369208bc371
commit: d892454b6814f07da676dae5e686cf221d34a1af selftests/vm/pkeys: exercise x86 XSAVE init state
date: 4 weeks ago
config: sparc64-randconfig-r023-20210726 (attached as .config)
compiler: sparc64-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d892454b6814f07da676dae5e686cf221d34a1af
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout d892454b6814f07da676dae5e686cf221d34a1af
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=sparc64 SHELL=/bin/bash -C tools/testing/selftests/vm install

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

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

Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for LOCKDEP
Depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT && (FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86)
Selected by
- PROVE_LOCKING && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
- LOCK_STAT && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
- DEBUG_LOCK_ALLOC && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' [ In reply to ]
On 7/26/21 8:11 PM, kernel test robot wrote:
>>> 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.
Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' [ In reply to ]
On 7/27/2021 10:52 PM, Dave Hansen wrote:
> On 7/26/21 8:11 PM, kernel test robot wrote:
>>>> 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.

Best Regards,
Rong Chen
Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' [ In reply to ]
On Wed, Aug 04 2021 at 17:04, Rong A. Chen wrote:
> On 7/27/2021 10:52 PM, Dave Hansen wrote:
>> On 7/26/21 8:11 PM, kernel test robot wrote:
>>>>> 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?

Thanks,

tglx
Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' [ In reply to ]
On 8/6/2021 8:42 PM, Thomas Gleixner wrote:
> On Wed, Aug 04 2021 at 17:04, Rong A. Chen wrote:
>> On 7/27/2021 10:52 PM, Dave Hansen wrote:
>>> On 7/26/21 8:11 PM, kernel test robot wrote:
>>>>>> 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
Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' [ In reply to ]
On Mon, Aug 09 2021 at 09:54, Rong A. Chen wrote:
> On 8/6/2021 8:42 PM, Thomas Gleixner wrote:
>> On Wed, Aug 04 2021 at 17:04, Rong A. Chen wrote:
>>> On 7/27/2021 10:52 PM, Dave Hansen wrote:
>>>> On 7/26/21 8:11 PM, kernel test robot wrote:
>>>>>>> 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:

Right. That's clearly broken because all these x8664 muck is derived
from:

MACHINE ?= $(shell echo $(uname_M) | sed -e 's/aarch64.*/arm64/' -e 's/ppc64.*/ppc64/')

which obviously fails for cross compiling because it's looking at the
compile machine and not at the target.

Something like the below should cure that, but TBH I lost track
which one of ARCH, SUBARCH, UTS_MACHINE should be used here. The kbuild
folks should know.

Thanks,

tglx

---
--- a/tools/testing/selftests/vm/Makefile
+++ b/tools/testing/selftests/vm/Makefile
@@ -4,7 +4,6 @@
include local_config.mk

uname_M := $(shell uname -m 2>/dev/null || echo not)
-MACHINE ?= $(shell echo $(uname_M) | sed -e 's/aarch64.*/arm64/' -e 's/ppc64.*/ppc64/')

# Without this, failed build products remain, with up-to-date timestamps,
# thus tricking Make (and you!) into believing that All Is Well, in subsequent
@@ -46,7 +45,7 @@ TEST_GEN_FILES += transhuge-stress
TEST_GEN_FILES += userfaultfd
TEST_GEN_FILES += split_huge_page_test

-ifeq ($(MACHINE),x86_64)
+ifeq ($(UTS_MACHINE),x86_64)
CAN_BUILD_I386 := $(shell ./../x86/check_cc.sh $(CC) ../x86/trivial_32bit_program.c -m32)
CAN_BUILD_X86_64 := $(shell ./../x86/check_cc.sh $(CC) ../x86/trivial_64bit_program.c)
CAN_BUILD_WITH_NOPIE := $(shell ./../x86/check_cc.sh $(CC) ../x86/trivial_program.c -no-pie)
@@ -68,7 +67,7 @@ TEST_GEN_FILES += $(BINARIES_64)
endif
else

-ifneq (,$(findstring $(MACHINE),ppc64))
+ifneq (,$(findstring $(UTS_MACHINE),ppc64))
TEST_GEN_FILES += protection_keys
endif

@@ -87,7 +86,7 @@ TEST_FILES := test_vmalloc.sh
KSFT_KHDR_INSTALL := 1
include ../lib.mk

-ifeq ($(MACHINE),x86_64)
+ifeq ($(UTS_MACHINE),x86_64)
BINARIES_32 := $(patsubst %,$(OUTPUT)/%,$(BINARIES_32))
BINARIES_64 := $(patsubst %,$(OUTPUT)/%,$(BINARIES_64))