linux-kernel - 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]

Message-ID: <efd7ab16-ed45-0ab0-a123-4e8e45c100d0@intel.com>
Date:   Tue, 27 Jul 2021 07:52:20 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     kernel test robot <lkp@...el.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>
Cc:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        Thomas Gleixner <tglx@...utronix.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: sparc64-linux-gcc: error: unrecognized command-line option
 '-mxsave'

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.