paperbot · PL 论文追踪

全部论文 待读 收藏

P2 MC Mutants: Evaluating and Improving Testing for Memory Consistency Specifications

MC Mutants:评估与改进内存一致性规范的测试
ASPLOS Proceedings of the 28th ACM International Conference on Architectural Support for Programming Languages and Operating Systems, Volume 22023匹配度 2/10 · 论文研究内存一致性规范的测试与变异方法,属于并发与内存模型方向,与用户关注的LLM/Agentic程序静态分析、浮点程序分析、贝叶斯程序分析等核心方向无直接关联。尽管涉及测试与调试,但未与机器学习或LLM交叉,因此匹配度低。引用 8 inbox
Reese Levine, Tianhao Guo, Mingun Cho, Alan Baker, Raph Levien, David Neto, Andrew Quinn, Tyler Sorensen
crossref: 2026-09-12

AI 速览

一句话:提出 MC Mutants,用变异方法评估并改进内存一致性规范测试,以发现既有测试遗漏的 MCS 缺陷。

共享内存平台通过内存一致性规范(MCS)让开发者推理并行程序行为,但确保平台符合 MCS 十分困难,实际平台中已出现大量 bug。现有 MCS 测试方法虽能发现缺陷,其有效性却依赖测试环境(如是否施加合成内存压力);同时,合法的 MCS 违规过于稀少,难以作为衡量测试效能的指标,导致既有方法遗漏关键 MCS bug。论文提出 MC Mutants,旨在通过变异体来评估并改进 MCS 测试,使测试环境与测试方法的有效性可被更可靠地度量和提升。摘要未报告具体实验结果。

问题
共享内存平台需符合内存一致性规范(MCS),但验证符合性困难;现有 MCS 测试效果依赖测试环境,且真实 MCS 违规稀少,难以作为效能指标,导致关键 bug 被遗漏。
方法
论文提出 MC Mutants,通过构造或注入 MCS 变异体来评估测试方法的有效性,并据此改进 MCS 测试环境与测试策略。
评估
以 MCS 变异体作为可度量的缺陷代理,评估测试环境对 MCS 测试效果的影响,弥补真实违规稀少带来的评估困难。
原文摘要(Abstract)

Shared memory platforms provide a memory consistency specification (MCS) so that developers can reason about the behaviors of their parallel programs. Unfortunately, ensuring that a platform conforms to its MCS is difficult, as is exemplified by numerous bugs in well-used platforms. While existing MCS testing approaches find bugs, their efficacy depends on the testing environment (e.g. if synthetic memory pressure is applied). MCS testing environments are difficult to evaluate since legitimate MCS violations are too rare to use as an efficacy metric. As a result, prior approaches have missed critical MCS bugs.

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot10000,
  title = {MC Mutants: Evaluating and Improving Testing for Memory Consistency Specifications},
  author = {Reese Levine and Tianhao Guo and Mingun Cho and Alan Baker and Raph Levien and David Neto and Andrew Quinn and Tyler Sorensen},
  booktitle = {ASPLOS},
  year = {2023},
  doi = {10.1145/3575693.3575750}
}