[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <74868f39491f8691afc5540f72679129@kernel.crashing.org>
Date: Sun, 12 Aug 2007 18:30:32 +0200
From: Segher Boessenkool <segher@...nel.crashing.org>
To: schwidefsky@...ibm.com
Cc: wjiang@...ilience.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
wensong@...ux-vs.org, heiko.carstens@...ibm.com,
linux-kernel@...r.kernel.org, ak@...e.de, cfriesen@...tel.com,
netdev@...r.kernel.org, horms@...ge.net.au,
akpm@...ux-foundation.org, Chuck Ebbert <cebbert@...hat.com>,
davem@...emloft.net, zlynx@....org, Chris Snook <csnook@...hat.com>
Subject: Re: [PATCH] make atomic_t volatile on all architectures
>> "+m" works. We use it. It's better than the alternatives. Pointing to
>> stale documentation doesn't change anything.
>
> Well, perhaps on i386. I've seen some older versions of the s390 gcc
> die
> with an ICE because I have used "+m" in some kernel inline assembly.
> I'm
> happy to hear that this issue is fixed in recent gcc. Now I'll have to
> find out if this is already true with gcc 3.x.
It was fixed (that is, "+m" is translated into a separate read
and write by GCC itself) in GCC-4.0.0, I just learnt.
> The duplication "=m" and "m" with the same constraint is rather
> annoying.
Yeah. Compiler errors are more annoying though I dare say ;-)
Segher
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists