From: Matthias Kaehlcke <mka@chromium.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [tip:x86/build 2/2] kernel/bounds.c:1: error: -mpreferred-stack-boundary=3 is not between 4 and 12
Date: Thu, 17 Aug 2017 09:57:21 -0700 [thread overview]
Message-ID: <20170817165721.GB173745@google.com> (raw)
In-Reply-To: <201708172209.HyH5F7Fu%fengguang.wu@intel.com>
El Thu, Aug 17, 2017 at 10:13:20PM +0800 kbuild test robot ha dit:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/build
> head: 8f91869766c00622b2eaa8ee567db4f333b78c1a
> commit: 8f91869766c00622b2eaa8ee567db4f333b78c1a [2/2] x86/build: Fix stack alignment for CLang
> config: x86_64-randconfig-b0-08172108 (attached as .config)
> compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
> reproduce:
> git checkout 8f91869766c00622b2eaa8ee567db4f333b78c1a
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> >> kernel/bounds.c:1: error: -mpreferred-stack-boundary=3 is not between 4 and 12
To be honest I was slightly concerned about not checking the actual
option that is applied, but expected it to be ok.
Though we can't use cc-option directly to chose between the gcc and
the clang option in this case we can use it to make sure only valid
parameters are applied. I'll prepare a fix for the fix.
Matthias
prev parent reply other threads:[~2017-08-17 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:13 kbuild test robot
2017-08-17 16:57 ` Matthias Kaehlcke [this message]
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=20170817165721.GB173745@google.com \
--to=mka@chromium.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tipbuild@zytor.com \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®