Happens-before memory model （HMM） is used as the basis of Java memory model （JMM）. Although HMM itself is simple, some complex axioms have to be introduced in JMM to prevent the causality loop, which causes absurd...Happens-before memory model （HMM） is used as the basis of Java memory model （JMM）. Although HMM itself is simple, some complex axioms have to be introduced in JMM to prevent the causality loop, which causes absurd out-of-thin-air reads that may break the type safety and se- curity guarantee of Java. The resulting JMM is complex and difficult to understand. It also has many anti-intuitive behav- iors, as demonstrated by the ＂ugly examples＂ by Aspinall and ~ev6~ [1]. Furthermore, HMM （and JMM） specifies only what execution traces are acceptable, but says nothing about how these traces are generated. This gap makes it difficult for static reasoning about programs. In this paper we present OHMM, an operational variation of HMM. The model is specified by giving an operational semantics to a language running on an abstract machine de- signed to simulate HMM. Thanks to its generative nature, the model naturally prevents out-of-thin-air reads. On the other hand, it uses a novel replay mechanism to allow instruc- tions to be executed multiple times, which can be used to model many useful speculations and optimization. The model is weaker than JMM for lockless programs, thus can accom- modate more optimization, such as the reordering of inde- pendent memory accesses that is not valid in JMM. Program behaviors are more natural in this model than in JMM, and many of the anti-intuitive examples in JMM are no longer valid here. We hope OHMM can serve as the basis for new memory models for Java-like languages.展开更多
文摘Happens-before memory model （HMM） is used as the basis of Java memory model （JMM）. Although HMM itself is simple, some complex axioms have to be introduced in JMM to prevent the causality loop, which causes absurd out-of-thin-air reads that may break the type safety and se- curity guarantee of Java. The resulting JMM is complex and difficult to understand. It also has many anti-intuitive behav- iors, as demonstrated by the ＂ugly examples＂ by Aspinall and ~ev6~ [1]. Furthermore, HMM （and JMM） specifies only what execution traces are acceptable, but says nothing about how these traces are generated. This gap makes it difficult for static reasoning about programs. In this paper we present OHMM, an operational variation of HMM. The model is specified by giving an operational semantics to a language running on an abstract machine de- signed to simulate HMM. Thanks to its generative nature, the model naturally prevents out-of-thin-air reads. On the other hand, it uses a novel replay mechanism to allow instruc- tions to be executed multiple times, which can be used to model many useful speculations and optimization. The model is weaker than JMM for lockless programs, thus can accom- modate more optimization, such as the reordering of inde- pendent memory accesses that is not valid in JMM. Program behaviors are more natural in this model than in JMM, and many of the anti-intuitive examples in JMM are no longer valid here. We hope OHMM can serve as the basis for new memory models for Java-like languages.
