Glauber de Oliveira Costa wrote: > I in fact have seen bugs with mixed reads and writes to the same cr, > (cr4), but adding the volatile > flag to the read function seemed to fix it.
Well, volatile will make a read be repeated rather than caching the previous value, but it has no effect on ordering. > Yet, I agree with you that > the theorectical problem exists for the reorder, and your proposed fix > seems fine (although if we're really desperate about memory usage, we > can use a char instead a int and save 3 bytes!) Sure. Ideally the compiler would never even generate a reference to it, and it could just be extern, but in practice the compiler will generate references sometimes. J ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel