On Mon, Jun 16, 2008 at 9:56 PM, Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx> wrote: > The compiler creates memory temporaries all the times and expects the > optimizers to see that the temporaries are not needed. However, > sometimes the temporaries aren't removed. It turns out this should never happen because raw_spinlock_t->lock is volatile. Therefore the memory clobber is not required. The memory barriers will prevent code from being moved before the lock or past the unlock. Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
