Critical Sections Are Not Per-Thread: A Trace Semantics for Lock-Based Concurrency
2026-03-16T08:52:06Z•fde2075810d0be1042d08813196b9cc945256d630d8be80958203febaf05d3bc
C/Pthreadsaxiomatic-semanticsconcurrencycritical-sectionsformal-methodslocksmemory-consistencyoperational-semanticsrace-detectiontrace-semanticsverification-toolsweak-memory
What happened
This document contains three arXiv CS/PL papers with relevance to concurrent and verification tooling: (1) “Critical Sections Are Not Per-Thread” presents a trace semantics for C/Pthread programs that removes the per-thread assumption for critical sections, showing critical sections may span multiple threads and exposing a semantic gap in the standard lock-set construction used by many race detectors and thread-safety analyses. This can cause existing tools that assume per-thread critical sections to miss races or report unsound guarantees in real C/Pthread code. (2) “Weak Memory Model Formals
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- arxiv_cs_pl
- Record identifier
- fde2075810d0be1042d08813196b9cc945256d630d8be80958203febaf05d3bc
- Enrichment time
- 2026-03-16T08:52:06Z
- AI-assisted enrichment
- Yes
This record may overlap with other records. Its enrichment can be incomplete or wrong, and machine assistance was used. Validate consequential decisions against the linked source and your own environment.