linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Chen, Rong A" <rong.a.chen@intel.com>,
	Dave Hansen <dave.hansen@intel.com>,
	kernel test robot <lkp@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
Date: Fri, 06 Aug 2021 14:42:36 +0200	[thread overview]
Message-ID: <87a6lu68xv.ffs@tglx> (raw)
In-Reply-To: <8bee8632-9129-bb02-ab94-f65786e65268@intel.com>

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


  reply	other threads:[~2021-08-06 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  3:11 kernel test robot
2021-07-27 14:52 ` Dave Hansen
2021-08-04  9:04   ` [kbuild-all] " Chen, Rong A
2021-08-06 12:42     ` Thomas Gleixner [this message]
2021-08-09  1:54       ` Chen, Rong A
2021-08-09 10:17         ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6lu68xv.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=rong.a.chen@intel.com \
    --subject='Re: [kbuild-all] Re: sparc64-linux-gcc: error: unrecognized command-line option '\''-mxsave'\''' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).