All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andi Kleen <ak@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: warning: read-write constraint -- 2.6.15-git8 onwards
Date: Wed, 18 Jan 2006 18:25:30 +0000	[thread overview]
Message-ID: <43CE881A.1060403@shadowen.org> (raw)

It seems that the following commit causes a bunch of warnings out of
most of the files in the kernel tree (see below for examples).  Backing
this out seems to cure them?

diff-tree 92934bcbf96bc9dc931c40ca5f1a57685b7b813b (from
636aab5ce332d88a76362797a55804c7da643467)`
tree eb9690ca6b23b5603429a8b3d290d6ca2545bcaf
parent 636aab5ce332d88a76362797a55804c7da643467
author Andi Kleen <ak@suse.de> 1137015752 +0100
committer Linus Torvalds <torvalds@g5.osdl.org> 1137034871 -0800

    [PATCH] i386/x86-64: Use input/output dependencies for bitops

    Noticed by Andreas Schwab

    Signed-off-by: Andi Kleen <ak@suse.de>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Compiled with:

    gcc version 3.3.4 (Debian 1:3.3.4-6sarge1)

-apw

  CC      arch/x86_64/kernel/process.o
include/asm/bitops.h: In function `default_idle':
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: In function `cpu_idle_wait':
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: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: In function `cpu_idle':
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: In function `set_personality_64bit':
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: In function `copy_thread':
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
  CC      arch/x86_64/kernel/signal.o
include/asm/bitops.h: In function `do_notify_resume':
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

             reply	other threads:[~2006-01-18 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 18:25 Andy Whitcroft [this message]
2006-01-19  3:03 ` warning: read-write constraint -- 2.6.15-git8 onwards Andi Kleen
2006-01-20 10:02   ` Jan Beulich

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=43CE881A.1060403@shadowen.org \
    --to=apw@shadowen.org \
    --cc=ak@suse.de \
    --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.