linux-kernel - Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 06 Aug 2021 14:42:36 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     "Chen, Rong A" <rong.a.chen@...el.com>,
        Dave Hansen <dave.hansen@...el.com>,
        kernel test robot <lkp@...el.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>
Cc:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized
 command-line option '-mxsave'

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