Hi...
isn't the barrier also for the compiler? IIRC, gcc reorder instructions in an attempt to optimize code. A memory-barrier will effectively stop the compiler for mixing code from before the barrier into the code afterwards.
Ah, yes I forgot that. thanks for reminding. regards, Mulyadi -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
