From: Andi Kleen <ak@suse.de>
To: Martin Bligh <mbligh@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: x86_64 compile spewing hundreds of warnings - started 2.6.15-git8
Date: Thu, 2 Mar 2006 20:49:57 +0100 [thread overview]
Message-ID: <200603022049.57969.ak@suse.de> (raw)
In-Reply-To: <440748FD.8010806@google.com>
On Thursday 02 March 2006 20:35, Martin Bligh wrote:
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
>
>
> What do these mean?
They mean you have a buggy compiler.
> And how do we get rid of it?
>
> Presumably caused by this:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=636dd2b7def5c9c72551b51d4d516a65c269de08
>
> or this:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=92934bcbf96bc9dc931c40ca5f1a57685b7b813b
It was the bitops.h constrain change.
The problem is that reverting them would be readding the problem. Maybe we need to
#ifdef it.
-Andi
next prev parent reply other threads:[~2006-03-02 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 19:35 x86_64 compile spewing hundreds of warnings - started 2.6.15-git8 Martin Bligh
2006-03-02 19:49 ` Andi Kleen [this message]
2006-07-31 16:14 ` Martin Bligh
2006-07-31 20:19 ` Andi Kleen
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=200603022049.57969.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.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