From: Andrew Morton <akpm@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
mjw99@ic.ac.uk
Subject: Re: [Bugme-new] [Bug 7602] New: Failure on compilation: include/asm/bitops.h:122: error: inconsistent operand constraints in an `asm' in nfs_access_add_cache()
Date: Thu, 30 Nov 2006 13:37:48 -0800 [thread overview]
Message-ID: <20061130133748.11261443.akpm@osdl.org> (raw)
In-Reply-To: <200611302118.kAULIrxS011661@fire-2.osdl.org>
On Thu, 30 Nov 2006 13:18:53 -0800
bugme-daemon@bugzilla.kernel.org wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=7602
>
> Summary: Failure on compilation: include/asm/bitops.h:122: error:
> inconsistent operand constraints in an `asm' in
> nfs_access_add_cache()
> Kernel Version: 2.6.19
> Status: NEW
> Severity: high
> Owner: trond.myklebust@fys.uio.no
> Submitter: mjw99@ic.ac.uk
>
>
> Most recent kernel where this bug did *NOT* occur:
> 2.6.18.3
>
> Distribution:
> RHEL4-U2 AS
>
> Hardware Environment:
> 8 CPU Dual Core Opteron box with 32Gb of ram
> http://www.iwill.net/product_2.asp?p_id=90&sp=Y
>
> Software Environment:
> RHEL4-U2
> gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
>
> Problem Description:
>
> Compilation fails with the error message:
> ....
> CC fs/nfs/client.o
> CC fs/nfs/dir.o
> fs/nfs/dir.c: In function `nfs_access_add_cache':
> include/asm/bitops.h:122: error: inconsistent operand constraints in an `asm'
Seems that this:
static __inline__ int __test_and_set_bit(int nr, volatile void * addr)
{
int oldbit;
__asm__(
"btsl %2,%1\n\tsbbl %0,%0"
:"=r" (oldbit),"+m" (ADDR)
:"dIr" (nr));
return oldbit;
}
explodes with gcc-3.4.4.
next parent reply other threads:[~2006-11-30 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611302118.kAULIrxS011661@fire-2.osdl.org>
2006-11-30 21:37 ` Andrew Morton [this message]
2006-11-30 22:22 ` Andi Kleen
2006-11-30 22:32 ` Andrew Morton
2006-11-30 22:49 ` Andi Kleen
2006-11-30 23:08 ` Randy Dunlap
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=20061130133748.11261443.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjw99@ic.ac.uk \
/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
all inboxes | Powered by JetHome®