From: Juergen Gross <jgross@suse.com>
To: mroos@linux.ee
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
peterz@infradead.org, x86@kernel.org
Subject: Re: cmpxchg.h:245:2: error: ‘asm’ operand has impossible constraints
Date: Thu, 6 Sep 2018 16:43:37 +0200 [thread overview]
Message-ID: <1c8dc5d4-e97c-274f-e6a4-a4e930ffa74f@suse.com> (raw)
In-Reply-To: <cfc3163c-40f2-ad5e-b303-bb8dc4288022@suse.com>
On 06/09/18 15:54, Juergen Gross wrote:
> Hey Meelis,
>
> On Mon, 27 Aug 2018, Meelis Roos wrote:
>
>> While trying to compile v4.18-13105-gaba16dc5cf93 with gcc 5.3.1 on a
>> 32-bit x86 configured for AMD K6
>> CC mm/slub.o
>> In file included from ./arch/x86/include/asm/atomic.h:8:0,
>> from ./include/linux/atomic.h:7,
>> from ./arch/x86/include/asm/thread_info.h:54,
>> from ./include/linux/thread_info.h:38,
>> from ./arch/x86/include/asm/preempt.h:7,
>> from ./include/linux/preempt.h:81,
>> from ./include/linux/spinlock.h:51,
>> from ./include/linux/mmzone.h:8,
>> from ./include/linux/gfp.h:6,
>> from ./include/linux/mm.h:10,
>> from mm/slub.c:13:
>> mm/slub.c: In function ‘__slab_free’:
>> ./arch/x86/include/asm/cmpxchg.h:245:2: error: ‘asm’ operand has
> impossible constraints
>> asm volatile(pfx "cmpxchg%c4b %2; sete %0" \
>
> Could you give the attched patch a try? I've been hit by this issue
> via kbuild robot complaining about one of my patches which didn't
> touch the asm stuff above.
>
> I suspect the "=a" contraint of the outputs and "a" of the inputs
> are the culprit. You could save me from having to search through
> all the debian repos for a gcc showing that issue...
You don't to test. I've installed a debian VM and could reproduce the
issue locally.
My patch changes the picture: instead of a build error gcc loops
forever.
Juergen
prev parent reply other threads:[~2018-09-06 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 21:27 cmpxchg.h:245:2: error: ‘asm’ operand has impossible constraints Meelis Roos
2018-08-31 20:01 ` Thomas Gleixner
2018-08-31 20:10 ` Meelis Roos
2018-08-31 20:30 ` Thomas Gleixner
[not found] ` <alpine.LRH.2.21.1808312335560.6505@math.ut.ee>
2018-08-31 20:43 ` Thomas Gleixner
2018-08-31 20:45 ` Meelis Roos
2018-09-06 13:54 ` Juergen Gross
2018-09-06 14:43 ` Juergen Gross [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=1c8dc5d4-e97c-274f-e6a4-a4e930ffa74f@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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