linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: cmpxchg.h:245:2: error: ‘asm’ operand has impossible constraints
Date: Fri, 31 Aug 2018 23:45:03 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1808312344390.6505@math.ut.ee> (raw)
In-Reply-To: <alpine.DEB.2.21.1808312240430.1349@nanos.tec.linutronix.de>

> > > > 5.3.1-14, seems to be available in 
> > > > http://snapshot.debian.org/package/gcc-5/5.3.1-14/#gcc-5_5.3.1-14 - the 
> > > > whole system is a snapshot of debian unstable when they stoooed 
> > > > supporting pre-686 CPUs.
> > > 
> > > Uurgh. That's going to be a nightmare to set that one up. Let's try to nail
> > > it on your machine then. Can you try to generate the intermediate file by
> > > invoking: make mm/slub.i ?
> > 
> > Here you are.
> 
> Looks unsuspicious. Is this an entitely new issue on 4.19-rc or can you see
> the same with older kernel versions?

4.18 was fine with sea same toolchain, so this is a new issue.

-- 
Meelis Roos (mroos@linux.ee)

  reply	other threads:[~2018-08-31 20:45 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 [this message]
2018-09-06 13:54   ` Juergen Gross
2018-09-06 14:43     ` Juergen Gross

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=alpine.LRH.2.21.1808312344390.6505@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).