Newshot

A Systematic Survey of Decompilation: Mapping Classical and Machine-Learning Approaches

Summary

arXiv:2611.21612v1 Announce Type: new Abstract: Context: Decompilers reconstruct source-level code from compiled binaries, and analysts rely on them whenever source code is unavailable. Many recent studies apply machine learning (ML), including large language models, to parts of this task. From the primary literature alone, it is unclear where these methods sit in the classical decompilation pipeline and how well their claims are supported. Objectives: We map decompilation research onto a pipeline-centered taxonomy and ask two questions: where classical, ML-trained, and ML-prompted approaches are positioned (RQ1), and how ML-based studies vary in technical design and evaluation evidence (RQ2). Methods: We surveyed 405 decompilation studies from 1973 to 2026, collected through database search and citation tracing. We classified 394 primary studies into eight pipeline stages and two complementary categories. For the 116 ML-based studies that propose or modify decompilation methods, we ex…

Original text(via arXiv cs.SE)

Computer Science > Software Engineering

Title:A Systematic Survey of Decompilation: Mapping Classical and Machine-Learning Approaches

Abstract:Context: Decompilers reconstruct source-level code from compiled binaries, and analysts rely on them whenever source code is unavailable. Many recent studies apply machine learning (ML), including large language models, to parts of this task. From the primary literature alone, it is unclear where these methods sit in the classical decompilation pipeline and how well their claims are supported. Objectives: We map decompilation research onto a pipeline-centered taxonomy and ask two questions: where classical, ML-trained, and ML-prompted approaches are positioned (RQ1), and how ML-based studies vary in technical design and evaluation evidence (RQ2). Methods: We surveyed 405 decompilation studies from 1973 to 2026, collected through database search and citation tracing. We classified 394 primary studies into eight pipeline stages and two complementary categories. For the 116 ML-based studies that propose or modify decompilation methods, we extracted the model-use strategy, reusable backbones, target platform, and the evidence behind each evaluation. Results: Classical techniques still dominate front-end recovery, IR lifting, and control-flow structuring (277 of 394 primary studies are classical). ML-based work (117 studies) clusters instead around symbol and name recovery, output refinement, and end-to-end translation. Type recovery is the clearest mixed region. Most ML-based studies target native binaries (97 of 116), and most evidence is item-level matching against references (89 of 116); execution-based tests, human or LLM judgment, and downstream-task evidence are much rarer. Conclusion: ML has not displaced the classical pipeline. It has been taken up where a recovered artifact can be posed as a prediction, translation, or refinement problem, and reported gains only make sense when read against the pipeline position and the evidence used to support them.
Subjects:Software Engineering (cs.SE)
Cite as:arXiv:2611.21612 [cs.SE]
(or arXiv:2611.21612v1 [cs.SE] for this version)
https://doi.org/10.48550/arXiv.2611.21612 arXiv-issued DOI via DataCite

Submission history

Access Paper:

  • HTML (experimental)

Additional Features

  • Audio Summary

Current browse context:

References & Citations

  • Google Scholar
  • Semantic Scholar

BibTeX formatted citation

Bookmark

Bibliographic and Citation Tools

Code, Data and Media Associated with this Article

Demos

Recommenders and Search Tools

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by arXiv cs.SE
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗