Re: [RFC/PATCH] doc: volatile considered evil

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 8 May 2007, Jeremy Fitzhardinge wrote:

> > You're point about reordering "asm volatile" constructs differs depending 
> > on -mvolatile-asm-stop or -mno-volatile-asm-stop, however.
> >   
> 
> Erm, that seems to be ia64 specific, and I have no idea what adding a
> "stop bit" implies.  Can you set even or odd parity too?
> 

It is analogous with a sequence point for ia64.  But, as you mentioned, it 
is ia64 specific so your comment about "asm volatile" constructs not being 
reordered is always appropriate outside of ia64 specific code but may not 
apply to ia64 if we ever compiled with -mvolatile-asm-stop.  If we do not
compile with that option, the behavior is unspecified.  I don't think 
we'll be adding -mvolatile-asm-stop support any time soon so your warning 
certainly is appropriate for all code at this time.

		David
-
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/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux