Messages in this thread | | | Date | Thu, 15 Jul 2010 07:34:44 -0700 | From | Jeremy Fitzhardinge <> | Subject | Re: [PATCH] x86: fix ordering constraints on crX read/writes |
| |
On 07/14/2010 06:29 PM, H. Peter Anvin wrote: > Yes, it will definitely NOT be pruned. I'm going to file a gcc documentation request to see if any of this is actually needed, though. There may also be a need for gcc to handle *inbound* general memory constraints. >
You mean "depends on all prior memory updates"? We have been relying on "memory" to do that (barrier(), for example), but it would be nice to explicitly confirm that's OK, or get something which is guaranteed to be OK.
J
| |