From: kbuild test robot <fengguang.wu@intel.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [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 22:13:20 +0800 [thread overview]
Message-ID: <201708172209.HyH5F7Fu%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
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
make[2]: *** [kernel/bounds.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +1 kernel/bounds.c
1cdf25d7 Christoph Lameter 2008-04-28 @1 /*
1cdf25d7 Christoph Lameter 2008-04-28 2 * Generate definitions needed by the preprocessor.
1cdf25d7 Christoph Lameter 2008-04-28 3 * This code generates raw asm output which is post-processed
1cdf25d7 Christoph Lameter 2008-04-28 4 * to extract and format the required data.
1cdf25d7 Christoph Lameter 2008-04-28 5 */
1cdf25d7 Christoph Lameter 2008-04-28 6
:::::: The code at line 1 was first introduced by commit
:::::: 1cdf25d704f7951d02a04064c97db547d6021872 kbuild: create a way to create preprocessor constants from C expressions
:::::: TO: Christoph Lameter <clameter@sgi.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33454 bytes --]
next reply other threads:[~2017-08-17 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:13 kbuild test robot [this message]
2017-08-17 16:57 ` Matthias Kaehlcke
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=201708172209.HyH5F7Fu%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=tipbuild@zytor.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®