A Problem-Oriented Perspective and Anchor Verification for Code Optimization
Tong Ye, Tengfei Ma, Xuhong Zhang, Hang Yu, Jianwei Yin, Wenhai Wang

TL;DR
This paper explores a new problem-oriented approach and an anchor verification framework to improve code optimization using LLMs, addressing local vs. global improvements and the challenge of optimization trade-offs.
Contribution
It introduces a problem-oriented perspective and anchor verification method, enabling global algorithmic improvements and reducing optimization trade-offs in code optimization with LLMs.
Findings
Enhanced correct optimization ratio
Increased speedup in code optimization
Effective mitigation of optimization tax
Abstract
Large Language Models (LLMs) have shown remarkable capabilities in solving various programming tasks, such as code generation. However, their potential for code optimization, particularly in performance enhancement, remains largely unexplored. This paper investigates the capabilities of LLMs in optimizing code for minimal execution time, addressing a critical gap in current research. The recently proposed code optimization methods construct program optimization pairs based on iterative submissions from the same programmer for the same problem. However, this approach confines LLMs to local performance improvements, neglecting global algorithmic innovation. To overcome this limitation, we adopt a completely different perspective by reconstructing the optimization pairs into a problem-oriented approach. This allows for the integration of various ideas from multiple programmers tackling the…
Peer Reviews
Decision·ICLR 2026 Poster
* The problem-oriented pairing is simple, scalable (pair count grows sharply with users per problem), and empirically yields more global, algorithmic improvements, which translate to strong %OPT/SPEEDUP gains after finetuning. * Anchor Verification cleverly reuses the slow reference to build verified test cases, outperforming self-debugging or direct test-generation baselines and improving %OPT, SPEEDUP, and CORRECT simultaneously.
* Evaluation centers on C/C++ competitive-programming style tasks compiled with -O3 on gem5. It’s unclear how PCO/Anchor Verification transfer to multi-file projects, diverse languages, library/API-heavy code, or system-level constraints. * To equalize counts, PCO keeps the top-speedup pairs per problem (to 78K), which may advantage PCO relative to PIE beyond perspective alone; more controls (e.g., random or stratified matching) would strengthen the causal claim. * EST@k relies on sampling w
- Novel and Intuitive Core Ideas: The two central contributions are well-motivated and insightful. The shift from a "user-oriented" to a "problem-oriented" perspective is a simple yet powerful reframing that directly tackles the issue of limited diversity in optimization strategies. The "anchor verification framework" is a practical and clever solution to the critical problem of correctness in automated optimization. - Comprehensive and Rigorous Evaluation: The paper's empirical evaluation is a
- The experiments are conducted on the PIE and PCO datasets, which are derived from competitive programming problems on CodeNet. While this is a suitable domain for studying algorithmic optimization, it raises questions about the generalizability of the findings. Real-world software optimization often involves different challenges, such as I/O bottlenecks, memory management, API usage, and interaction with large codebases, which are not well-represented in this setting. The effectiveness of the
- The paper is well-written. - The idea of a problem-oriented perspective is sound and clear. It can help LLMs to learn how to optimize code by different coding styles. - Valid approach to ensure code correctness by anchor verification.
- While this work has considerable potential for improvement, a primary concern from the reviewer is that one drawback of problem-oriented data collection is that the dataset may contain pairs of code that are too dissimilar, despite solving the same coding problem. For example, the proposed strategy of data collection can produce code pairs that differ significantly in terms of variable declaration and readability level, which may increase the risk of confusing the LLMs during fine-tuning. - Wh
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsModel-Driven Software Engineering Techniques
MethodsFocus
