From: Dave Hansen <dave.hansen@intel.com>
To: kernel test robot <lkp@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
Date: Tue, 27 Jul 2021 07:52:20 -0700 [thread overview]
Message-ID: <efd7ab16-ed45-0ab0-a123-4e8e45c100d0@intel.com> (raw)
In-Reply-To: <202107271153.7QWf3g6F-lkp@intel.com>
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.
next prev parent reply other threads:[~2021-07-27 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 3:11 sparc64-linux-gcc: error: unrecognized command-line option '-mxsave' kernel test robot
2021-07-27 14:52 ` Dave Hansen [this message]
2021-08-04 9:04 ` [kbuild-all] " Chen, Rong A
2021-08-06 12:42 ` Thomas Gleixner
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=efd7ab16-ed45-0ab0-a123-4e8e45c100d0@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--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=tglx@linutronix.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).