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.
VLDB 2026 Research / reviewers in the wild / expert

Jean-Phillipe Martin

dblp:82/7790 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2010
—ORCID · none

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

Software engineering, systems software and programming languages · 1 · 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
1 paper
Concurrent programming · 50% Program verification · 50%
Network and information security
1 paper
Systems and software security · 100%

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

TopicWeightPapersLastEvidence papers
Systems and software security
memory safety		 0.112010
Dynamically checking ownership policies in concurrent c/c++ programs · POPL 2010
Concurrent programming › concurrency bugs
data races		 0.112010
Dynamically checking ownership policies in concurrent c/c++ programs · POPL 2010
Program verification
dynamic verification		 0.112010
Dynamically checking ownership policies in concurrent c/c++ programs · POPL 2010

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

dynamic analysis · 0.2
YearPublicationVenuePosition
2010 Dynamically checking ownership policies in concurrent c/c++ programs
abstract
Concurrent programming errors arise when threads share data incorrectly. Programmers often avoid these errors by using synchronization to enforce a simple ownership policy: data is either owned exclusively by a thread that can read or write the data, or it is read owned by a set of threads that can read but not write the data. Unfortunately, incorrect synchronization often fails to enforce these policies and memory errors in languages like C and C++ can violate these policies even when synchronization is correct.
Jean-Phillipe Martin, Michael Hicks 0001, Manuel Costa, Periklis Akritidis, Miguel Castro 0001
 POPL1