Extracting Compiler Provenance from Program Binaries.¶

Rosenblum, N. E., Miller, B. P., & Zhu, X. (2010). Extracting Compiler Provenance from Program Binaries. Proceedings of the 9th ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering (PASTE), 21-28.

Type: Conference paper
Intellectual base: Primary research
Year: 2010
Pages: 21-28
DOI: 10.1145/1806672.1806678
DOI registrant: Association for Computing Machinery
Link: https://doi.org/10.1145/1806672.1806678
Cited from: criminology_forensic

Cited by¶

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Primes¶

Production Signature
- Code style / programmer fingerprinting — naming defaults, comment style, and error-handling habits recur across a programmer's code at non-trivial attribution accuracy. Compiler / model fingerprinting — optimized binaries carry the compiler's fingerprint; large language models leave detectable statistical signatures distinguishing model families.
  This sourceShows optimized binaries carry the source compiler's identifiable fingerprint, recovered at over 90% accuracy by structured learning over instruction patterns.
  
  Supported in partVerified against the work's full text
  
  Rosenblum et al. show binaries carry compiler-identifiable idiom patterns recoverable at over 90% accuracy; the paper says nothing about LLM fingerprints or code-style attribution.
  
  “showing that our models identify the source compiler of binary code with over 90% accuracy”
  From the work's full text.
  
  Read by an automated reader; not a human review. How support was checked

Verification¶

Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:d42f05f17b44 · see in the full table