A type and effect system for atomicity

By Cormac Flanagan, Shaz Qadeer. ACM-SIGPLAN Symposium on Programming Language Design and Implementation, 2003

404 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Hardware and Architecture

View Paper: https://www.semanticscholar.org/paper/5fdf82c64f77b61f4e4b6c1f71f01feb9207a219

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

1. Shaz Qadeer
2. Koushik Sen
3. Dinghao Wu
4. Shan Lu
5. Yuanyuan Zhou
6. Cormac Flanagan
7. Stephen N. Freund
8. A. Aiken

In Hardware and Architecture

1. Koushik Sen
2. Shaz Qadeer
3. Dinghao Wu
4. Yuanyuan Zhou
5. Shan Lu
6. Cormac Flanagan
7. Stephen N. Freund
8. Soyeon Park

Citations in the corpus

• KISS: keep it simple and sequential (2004, methodology): “[20] C. Flanagan and S. Qadeer.”
• Unbounded transactional memory (2005, background): “The “Oversized xaction,” “Biggest xaction,” and “Overflow %” columns show that some applications contain transactions whose footprints would overflow any reasonably-sized cache.”
• CTrigger: exposing atomicity violation bugs from their hiding places (2009, background): “Without CTrigger, some of these bugs do not manifest even after 7 full days of stress testing.”
• AVIO: detecting atomicity violations via access interleaving invariants (2006, neutral): “Atomicity Violation Detection Several static and dynamic techniques based on state reduction theory of right/left mover have been proposed [12, 33, 39] to detect atomicity violations.”
• Race directed random testing of concurrent programs (2008, background): “Such sets of problematic statements could be provided by a static or dynamic analysis technique [23, 22, 2].”
• Atomizer: a dynamic atomicity checker for multithreaded programs (2004, methodology): “A comparable error in PrintWriter had been previously identified by a static type system [24], but the Atomizer caught this defect with no programmer intervention and pinpointed an exact location i n the program where the bug could manifest itself.”
• Effective static race detection for Java (2006, background): “Recent work on verification of concurrent programs has focused on checking atomicity [2, 18, 22, 24–26, 44, 51, 52].”