From: Will Deacon <will.deacon@arm.com>
To: kbuild test robot <lkp@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: arch/x86/include/asm/rmwcc.h:23:17: error: jump into statement expression
Date: Thu, 1 Nov 2018 09:22:18 +0000 [thread overview]
Message-ID: <20181101092217.GB1565@brain-police> (raw)
In-Reply-To: <201811010946.KVmoo2CH%fengguang.wu@intel.com>
Peter,
On Thu, Nov 01, 2018 at 09:11:52AM +0800, kbuild test robot wrote:
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 5b7449810ae6d652629c550d3974c8453836d229
> commit: 7aa54be2976550f17c11a1c3e3630002dea39303 locking/qspinlock, x86: Provide liveness guarantee
> date: 2 weeks ago
> config: x86_64-randconfig-j0-10290909 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
> git checkout 7aa54be2976550f17c11a1c3e3630002dea39303
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> In file included from arch/x86/include/asm/atomic.h:5:0,
> from include/linux/atomic.h:7,
> from include/linux/crypto.h:20,
> from arch/x86/kernel/asm-offsets.c:9:
> arch/x86/include/asm/qspinlock.h: In function 'queued_fetch_set_pending_acquire':
> >> arch/x86/include/asm/rmwcc.h:23:17: error: jump into statement expression
> : clobbers : cc_label); \
You wrote a fix for this last week, right? Do we need to get it queued
someplace for -rc1?
Will
next prev parent reply other threads:[~2018-11-01 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 1:11 kbuild test robot
2018-11-01 9:22 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-31 3:20 kbuild test robot
2018-10-30 1:51 kbuild test robot
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=20181101092217.GB1565@brain-police \
--to=will.deacon@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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®