A Java bytecode optimizer using side-effect analysis

Clausen, Lars

doi:10.1002/(sici)1096-9128(199711)9:11<1031::aid-cpe354>3.0.co;2-o

Cited by 46 publications

(36 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…If Sj is a non-variable type, then from the induction hypothesis, we also have (9). Using, (7), (8), and (9), we proved (4) for this j.…”

Section: Subtypingmentioning

confidence: 66%

“…Immutability information is useful in many software engineering tasks, such as modeling [7], verification [30], compile-and runtime optimizations [9,25,28], refactoring [17], test input generation [1], regression oracle creation [24,32], invariant detection [15], specification mining [10], and program comprehension [13]. Three varieties of immutability guarantee are: Class immutability No instance of an immutable class may be changed; examples in Java include String and most subclasses of Number such as Integer and BigDecimal.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Object and reference immutability using Java generics

Zibin

Potanin

Ali

et al. 2007

Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the F

View full text Add to dashboard Cite

A compiler-checked immutability guarantee provides useful documentation, facilitates reasoning, and enables optimizations. This paper presents Immutability Generic Java (IGJ), a novel language extension that expresses immutability without changing Java's syntax by building upon Java's generics and annotation mechanisms. In IGJ, each class has one additional type parameter that is Mutable, Immutable, or ReadOnly. IGJ guarantees both reference immutability (only mutable references can mutate an object) and object immutability (an immutable reference points to an immutable object). IGJ is the first proposal for enforcing object immutability within Java's syntax and type system, and its reference immutability is more expressive than previous work. IGJ also permits covariant changes of type parameters in a type-safe manner, e.g., a readonly list of integers is a subtype of a readonly list of numbers. IGJ extends Java's type system with a few simple rules. We formalize this type system and prove it sound. Our IGJ compiler works by typeerasure and generates byte-code that can be executed on any JVM without runtime penalty.

show abstract

“…If Sj is a non-variable type, then from the induction hypothesis, we also have (9). Using, (7), (8), and (9), we proved (4) for this j.…”

Section: Subtypingmentioning

confidence: 66%

Section: Introductionmentioning

confidence: 99%

Object and reference immutability using Java generics

Zibin

Potanin

Ali

et al. 2007

Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the F

View full text Add to dashboard Cite

show abstract

“…The advantage of this, as discussed in §1, is that it lends itself more easily to modular checking. Clausen developed a Java bytecode optimiser using SCHA which exploits knowledge of side-effects [9]. In particular, it determines whether a method's receiver and parameters are pure, read-only, write-only or read-write.…”

Section: Related Workmentioning

confidence: 99%

“…Knowing which methods are pure in a program has a variety of applications, such as: specification languages [19,1,3,10], model checking [31], compiler optimisations [9,18,36], atomicity [13], query systems [21,34] and memoisation of function calls [15].…”

Section: Introductionmentioning

confidence: 99%

JPure: A Modular Purity System for Java

Pearce

2011

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Purity Analysis is the problem of determining whether or not a method may have side-effects. This has applications in automatic parallelisation, extended static checking, and more. We present a novel purity system for Java that employs purity annotations which can be checked modularly. This is done using a flow-sensitive, intraprocedural analysis. The system exploits two properties, called freshness and locality, to increase the range of methods that can be considered pure. JPure also includes an inference engine for annotating legacy code. We evaluate our system against several packages from the Java Standard Library. Our results indicate it is possible to uncover significant amounts of purity efficiently.

show abstract

“…Knowing which method parameters are accessed in a read-only way, and which ones may be modified, is useful in many software engineering tasks, such as modeling [4], verification [24], compiler optimizations [6,21], program transformations [12], test input generation [1], regression oracle creation [14,27], invariant detection [11], specification mining [7], and program comprehension [10].…”

Section: Introductionmentioning

confidence: 99%