Detecting Read-Only Methods in Java

Detecting Read-Only Methods in Java (2000)

by Jeff Bogda

Venue:	In Proc. of the ACM Workshop on Languages, Compilers, and Runtime Systems for Scalable Computers (LCR 2000
Citations:	2 - 0 self

User correction supplied by SystemCorrections

Datum	Value	Source
TITLE	Detecting Read-Only Methods in Java	user correction - Legacy Corrections
AUTHOR NAME	Jeff Bogda	SVM HeaderParse 0.1
AUTHOR AFFIL	Department of Computer Science; University of California	SVM HeaderParse 0.2
AUTHOR ADDR	Santa Barbara, CA 93106	SVM HeaderParse 0.1
ABSTRACT	. One typically defines a read-only method as a method that does not perform any write operations; however, with respect to a multi-threaded program, we augment this interpretation and let a read-only method be one that does not write to a memory location visible to more than one thread. Such a method can execute concurrently with other read-only methods. With the relaxation of mutual exclusion in mind, we present a read-write analysis that employs the ideas of shape analysis and escape analysis to identify readonly methods in Java. Approximately 31% of the methods in the JDK 1.2 core libraries meets this definition of read-only---nearly 50% more than those that do not perform any write operations. 1	user correction - Legacy Corrections
YEAR	2000	INFERENCE
VENUE	In Proc. of the ACM Workshop on Languages, Compilers, and Runtime Systems for Scalable Computers (LCR 2000	INFERENCE
VENUE TYPE	CONFERENCE	INFERENCE
PAGES	64--69	INFERENCE
CITATIONS	14 found	ParsCit 1.0