From: Martin Bligh <mbligh@google.com>
To: Martin Bligh <mbligh@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: x86_64 compile spewing hundreds of warnings - started 2.6.15-git8
Date: Mon, 31 Jul 2006 09:14:25 -0700 [thread overview]
Message-ID: <44CE2C61.4010809@google.com> (raw)
In-Reply-To: <440748FD.8010806@google.com>
Martin Bligh wrote:
> between 2.6.15-git7 and 2.6.15-git8 we started getting hundreds of
> compile warnings:
>
> -git7: http://test.kernel.org/20295/debug/test.log.0
> -git8: http://test.kernel.org/20402/debug/test.log.0
>
> Warnings look like this:
>
> include/asm/bitops.h: In function `load_elf32_binary':
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a
> register
>
>
> What do these mean? 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
>
>
There were rumblings about changing these checks around a bit, but
nothing happened and the warnings are still there ... any chance of
fixing this?
M.
next prev parent reply other threads:[~2006-07-31 16:14 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
2006-07-31 16:14 ` Martin Bligh [this message]
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=44CE2C61.4010809@google.com \
--to=mbligh@google.com \
--cc=ak@suse.de \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.