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

Jan Wen Voung

dblp:53/4167 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 2008
—ORCID · none

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

Software engineering, systems software and programming languages · 2 · 1 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
Program analysis · 50% Concurrent programming · 50%

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

TopicWeightPapersLastEvidence papers
Program analysis
data flow analysis
0.112008
Dataflow analysis for concurrent programs using datarace detection · PLDI 2008
Concurrent programming › concurrency bug detection
data race detection
0.112008
Dataflow analysis for concurrent programs using datarace detection · PLDI 2008
Concurrent programming › concurrency bugs
data races
0.112007
RELAY: static race detection on millions of lines of code · ESEC/SIGSOFT FSE 2007
Program analysis › concurrent program analysis
static race detection
0.112007
RELAY: static race detection on millions of lines of code · ESEC/SIGSOFT FSE 2007

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

data-race detection · 0.1data flow analysis · 0.1static analysis · 0.1modular analysis · 0.1
YearPublicationVenuePosition
2008 Dataflow analysis for concurrent programs using datarace detection
abstract
Dataflow analyses for concurrent programs differ from their single-threaded counterparts in that they must account for shared memory locations being overwritten by concurrent threads. Existing dataflow analysis techniques for concurrent programs typically fall at either end of a spectrum: at one end, the analysis conservatively kills facts about all data that might possibly be shared by multiple threads; at the other end, a precise thread-interleaving analysis determines which data may be shared, and thus which dataflow facts must be invalidated. The former approach can suffer from imprecision, whereas the latter does not scale.
Ravi Chugh, Jan Wen Voung, Ranjit Jhala, Sorin Lerner
PLDI2
2007 RELAY: static race detection on millions of lines of code
abstract
Data races occur when multiple threads are about to access the same piece of memory, and at least one of those accesses is a write. Such races can lead to hard-to-reproduce bugs that are time consuming to debug and fix. We present RELAY, a static and scalable race detection analysis in which unsoundness is modularized to a few sources. We describe the analysis and results from our experiments using RELAY to find data races in the Linux kernel, which includes about 4.5 million lines of code.
Jan Wen Voung, Ranjit Jhala, Sorin Lerner
ESEC/SIGSOFT FSE1