REVIEW 5 cited by
AlphaTrans: A Neuro-Symbolic Compositional Approach for Repository-Level Code Translation and Validation
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
Code translation transforms programs from one programming language (PL) to another. Several rule-based transpilers have been designed to automate code translation between different pairs of PLs. However, the rules can become obsolete as the PLs evolve and cannot generalize to other PLs. Recent studies have explored the automation of code translation using Large Language Models (LLMs). One key observation is that such techniques may work well for crafted benchmarks but fail to generalize to the scale and complexity of real-world projects with dependencies, custom types, PL-specific features, etc. We propose AlphaTrans, a neuro-symbolic approach to automate repository-level code translation. AlphaTrans translates both source and test code, and employs multiple levels of validation to ensure the translation preserves the functionality of the source program. To break down the problem for LLMs, AlphaTrans leverages program analysis to decompose the program into fragments and translates them in the reverse call order. We leveraged AlphaTrans to translate ten real-world open-source projects consisting of <836, 8575, 2719> classes, methods, and tests. AlphaTrans breaks down these projects into 17874 fragments and translates the entire repository. 96.40% of the translated fragments are syntactically correct, and AlphaTrans validates the translations' runtime behavior and functional correctness for 27.03% and 25.14% of fragments. On average, the integrated translation and validation take 34 hours to translate a project, showing its scalability in practice. For the incorrect translations, AlphaTrans generates a report including existing translation, stack trace, test errors, or assertion failures. We provided these artifacts to two developers to fix the translation bugs in four projects. They were able to fix the issues in 20.1 hours on average and achieve all passing tests.
Forward citations
Cited by 5 Pith papers
-
ParEval-Repo: A Benchmark Suite for Evaluating LLMs with Repository-level HPC Translation Tasks
A benchmark and evaluation showing that LLM-based repository-scale HPC translation works for small programs but fails for larger ones due to build system and cross-file issues.
-
MigrationBench: Repository-Level Code Migration Benchmark from Java 8
MigrationBench provides 5,102 real Maven repositories as a Java 8 to Java 17 migration benchmark, plus an evaluation framework and an LLM feedback agent that achieves 62.33% minimal and 27.33% maximal migration succes...
-
DI-BENCH: Benchmarking Large Language Models on Dependency Inference with Testable Repositories at Scale
A new large-scale benchmark shows that current large language models pass under half of repository execution tests when asked to infer dependencies.
-
Syzygy: Dual Code-Test C to (safe) Rust Translation using LLMs and Dynamic Analysis
A dual code-and-test generation pipeline with dynamic-analysis specifications translates the 3,000-line Zopfli C library into safe Rust, though the top-level validation compares compression ratios rather than exact outputs.
-
A Pilot Study on LLM-Based Agentic Translation from Android to iOS: Pitfalls and Insights
A five-project pilot study found that a GPT-4o agent pipeline translates 70.7% of Android files to valid Swift after automated validation, with failures concentrated in internal references and platform-specific APIs.
Discussion (0). Continue with ORCID to comment.