From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: read-write constraint warnings
Date: Thu, 13 Apr 2006 19:47:41 +0100 [thread overview]
Message-ID: <200604131947.41199.nick@linicks.net> (raw)
Hi all,
I see this has been raised before, but could not find a closure thread:
e.g.
include/asm/bitops.h:79: warning: read-write constraint does not allow a
register
Since moving 2.6.15.7 --> 2.6.16.4 I get truck loads of these warnings.
nick@linuxamd:linux$ gcc -v
Reading specs from /usr/lib/gcc/i486-slackware-linux/3.4.0/specs
Configured
with: ../gcc-3.4.0/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 3.4.0
nick@linuxamd:linux$ ld -v
GNU ld version 2.15.90.0.3 20040415
There is no problem as kernels built with these warnings are fine, so a GCC
issue I presume?
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
reply other threads:[~2006-04-13 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200604131947.41199.nick@linicks.net \
--to=nick@linicks.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox