Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Andrew J. McPherson

dblp:17/11411 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2016
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 2 · 2 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Concurrent programming · 100%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Concurrent programming › memory models
fence insertion
0.522016
Fence Placement for Legacy Data-Race-Free Programs via Synchronization Read Detection · ACM Trans. Archit. Code Optim. 2016
Fence placement for legacy data-race-free programs via synchronization read detection · PPoPP 2015
Concurrent programming
memory models
0.522016
Fence Placement for Legacy Data-Race-Free Programs via Synchronization Read Detection · ACM Trans. Archit. Code Optim. 2016
Fence placement for legacy data-race-free programs via synchronization read detection · PPoPP 2015

Methods — techniques the papers use, named apart from their topics

fence placement · 0.2LLVM · 0.2static analysis · 0.2
YearPublicationVenuePosition
2016 Fence Placement for Legacy Data-Race-Free Programs via Synchronization Read Detection
abstract
Shared-memory programmers traditionally assumed Sequential Consistency (SC), but modern systems have relaxed memory consistency. Here, the trend in languages is toward Data-Race-Free (DRF) models, where, assuming annotated synchronizations and the program being well-synchronized by those synchronizations, the hardware and compiler guarantee SC. However, legacy programs lack annotations, so even well-synchronized (legacy DRF) programs aren’t recognized. For legacy DRF programs, we can significantly prune the set of memory orderings determined by automated fence placement by automatically identifying synchronization reads. We prove our rules for identifying them conservatively, implement them within LLVM, and observe a 30% average performance improvement over previous techniques.
Andrew J. McPherson, Vijay Nagarajan, Susmit Sarkar, Marcelo Cintra
ACM Trans. Archit. Code Optim.1
2015 Fence placement for legacy data-race-free programs via synchronization read detection
abstract
Fence placement is required to ensure legacy parallel programs operate correctly on relaxed architectures. The challenge is to place as few fences as possible without compromising correctness. By identifying necessary conditions for a read to be an acquire we improve upon the state of the art for legacy DRF programs by up to 2.64x.
Andrew J. McPherson, Vijay Nagarajan, Susmit Sarkar, Marcelo Cintra
PPoPP1