The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
The Java memory model described in Chapter 17 of the Java Language Specification gives constraints on how threads interact through memory. The Java memory model is hard to interpret and poorly understood; it imposes constraints that prohibit common compiler optimizations and are expensive to implement on existing hardware. At least one shipping optimizing Java compiler violates the constraints of the existing Java memory model. These issues are particularly important for high-performance Java applications, since they are more likely to use and need aggressive optimizing compilers and parallel processors. In addition, programming idioms used by some programmers and used within Sun's Java Development Kit is not guaranteed to be valid according the existing Java memory model. This paper reviews these issues and suggests replacement memory models for Java. 1 Introduction The Java memory model, as described in chapter 17 of the Java Language Specification [GJS96], is very hard to unders...
How it got here
How it got here
agent via openalex
Added
2026-10-26 12:50 UTC
Not denied by
a person 2026-10-29 17:12 UTC
Cite it as
@misc{pugh1999fixing,
title = {Fixing the Java memory model},
author = {William Pugh},
year = {1999},
pages = {89--98},
doi = {10.1145/304065.304106},
}