On Sun, 12 Aug 2007, Martin Schwidefsky wrote: > > The duplication "=m" and "m" with the same constraint is rather > annoying. It's not only annoying, it causes gcc to generate bad code too. At least certain versions of gcc will generate the address *twice*, even if there is obviously only one address used. If you have problems with "+m", you are often actually better off using just "m" and then adding a memory clobber. But that has other code generation downsides. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] make atomic_t volatile on all architectures
- From: Chris Snook <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Chris Snook <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Chuck Ebbert <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Martin Schwidefsky <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Segher Boessenkool <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] make atomic_t volatile on all architectures
- From: Martin Schwidefsky <[email protected]>
- [PATCH] make atomic_t volatile on all architectures
- Prev by Date: Re: Problems with USB disk
- Next by Date: Re: [PATCH] Fix triplefault on x86-64 bootup
- Previous by thread: Re: [PATCH] make atomic_t volatile on all architectures
- Next by thread: Re: [PATCH] make atomic_t volatile on all architectures
- Index(es):
 |