Why is it not possible to just adopt the Java memory model?
The Java memory model was heavily motivated by the desire to preserve both type-safety and some other security guarantees, both of which are essential if untrusted code is to be run in the same address space with trusted code. Since this is in any case impossible for ordinary C or C++ code, this is no longer a consideration. Furthermore, it appears that making Java-like guarantees for C++ is potentially expensive, particularly on architectures that provide a weak memory model, or weak atomicity guarantees for ordinary stores. For example, implementations would have to ensure that an object pointer cannot be passed from one thread to another without previously making the objects vtable pointer visible to the other thread. This is likely to require a memory barrier during object construction. And C++ programmers, unlike Java programmers, tend to expect object construction to be a very light-weight operation. It does however appear more and more likely that we will borrow heavily from the