Main ConferenceCGO 2026

Accepted Papers

Call for Papers

IEEE/ACM International Symposium on Code Generation and Optimization (CGO)

Co-located with HPCA, PPoPP, and CC

Sydney, Australia

The International Symposium on Code Generation and Optimization (CGO’26) will be held in Sydney, Australia. CGO is the premier venue to bring together researchers and practitioners working at the interface of hardware and software on a wide range of optimization and code generation techniques and related issues. The conference spans the spectrum from purely static to fully dynamic approaches, and from pure software-based methods to specific architectural features and support for code generation and optimization.

Important dates

CGO uses two submissions per year.

This follows the model established by other conferences in our field in recent years, such as ASPLOS and OOPSLA. Papers submitted to the first round can either be directly accepted, rejected, or invited to submit a revised version of the paper to the second round. Papers rejected in the first round may not be submitted to the second round. For papers invited to submit a revised version, authors will be given a list of revisions that should be acted on to improve the paper. We will make every effort to ensure that the revised paper is reviewed by the same reviewers (and possibly additional reviewers), who will assess whether the revisions are satisfactory. If so, the paper will be accepted. If the revised paper is rejected, the authors may submit a further revised version in a subsequent round, which will be treated as a new submission.

First Submission Deadline

• Paper Submission: 29 May 2025
• Author Rebuttal Period: 8–10 July 2025
• Paper Notification: 21 July 2025

Second Submission Deadline

• Paper Submission: 11 September 2025
• Author Rebuttal Period: 21–23 October 2025
• Paper Notification: 3 November 2025

Contacts:

• Timothy M. Jones, University of Cambridge - timothy.jones@cl.cam.ac.uk
• Albert Cohen, Google - albertcohen@google.com

Topics

Original contributions are solicited on, but not limited to, the following topics:

• Code generation, translation, transformation, and optimization for performance, energy, virtualization, portability, security, or reliability concerns, and architectural support
• Efficient execution of dynamically typed and higher-level languages
• Optimization and code generation for emerging programming models, platforms, domain-specific languages
• Dynamic, static, profile-guided and feedback-directed optimization
• Machine-learning-based code generation, analysis, transformation and optimization
• Static, dynamic, and hybrid analysis for performance, energy, memory locality, throughput or latency, security, reliability, or functional debugging
• Program characterization methods
• Profiling and instrumentation techniques and architectural support for them
• Novel and efficient tools
• Compiler design, practice and experience
• Compiler abstraction and intermediate representations
• Vertical integration of language features, representations, optimizations, and runtime support for parallelism
• Solutions that involve cross-layer (HW/OS/VM/SW) design and integration
• Deployed dynamic/static compiler and runtime systems for general purpose, embedded system and cloud / HPC platforms
• Parallelism, heterogeneity, and reconfigurable architectures
• Optimizations for heterogeneous or specialized targets, GPUs, SoCs, CGRA and quantum computers
• Compiler support for vectorization, thread extraction, task scheduling, speculation, transaction, memory management, data distribution and synchronization

Paper types

Papers submitted to CGO can be standard research papers, tools papers or practical experience papers. All must be written in the IEEE conference format (use the conference mode), and may have up to 10 pages, references excluded. Supplementary materials may be included as an Appendix at the end of the submitted paper. The Appendix has no page limit, but the text of the full paper excluding the Appendix must fit within 10 pages. Reviewers are not required to read the Appendix and may do so at their discretion. In other words, papers must be self-contained without needing to read any material in the Appendix.

Please ensure that you and your co-authors obtain an ORCID ID, so you can complete the publishing process for your accepted paper. We are committed to improve author discoverability, ensure proper attribution and contribute to ongoing community efforts around name normalization; your ORCID ID will help in these efforts.

Please be mindful of the IEEE publishing policies when preparing and submitting your article.

Tool papers

Tool papers must give a clear account of a new tool’s functionality. They must describe the problem that the tool helps to solve, how the tool works and provide an evaluation of the tool. There does not have to be novel research in the way the tool works, but it does have to solve a novel problem or in a novel (and better) way compared to existing tools. A good tools paper will:

• Frame the problem that the tool solves, showing that it is an important subject
• Describe how the tool works to solve the problem
• Evaluate the ability of the tool to solve the problem
• Possibly provide case studies of using the tool, showing what improvements can be made now the problem has been ameliorated.

Tools paper authors should prepend their paper title with ‘Tool:’ to provide clarity that this is a tools paper during the review process (this can be removed for the final camera-ready paper).

The successful evaluation of an artifact is mandatory for a Tool Paper. Therefore, authors of work conditionally accepted as Tool Papers must submit an artifact to the Artifact Evaluation Committee. The successful evaluation of the artifact is a requirement for final acceptance.

The selection criteria for papers in this category are:

• Originality: Papers should present CGO-related technologies applied to real-world problems with scope or characteristics that set them apart from previous solutions.
• Usability: The presented tool or compiler should have broad usage or applicability. They are expected to assist in CGO-related research, or could be extended to investigate or demonstrate new technologies. If significant components are not yet implemented, the paper will not be considered.
• Documentation: The tool or compiler should be presented on a web-site giving documentation and further information about the tool.
• Benchmark Repository: A suite of benchmarks for testing should be provided.
• Availability: The tool or compiler should be available for public use.
• Foundations: Papers should incorporate the principles underpinning Code Generation and Optimization (CGO). However, a thorough discussion of theoretical foundations is not required; a summary of such should suffice.
• Artifact Evaluation: The submitted artifact must be functional and support the claims made in the paper.

Practical experience papers

Practical experience papers should summarize a practical experience with realistic case studies. They must make it clear where the novelty in the work comes from, which could be from applying known techniques to a new system (with novel features), from finding new ways to implement existing analyses or transformations in a unique way, or from applying established schemes to draw new conclusions about them.

Practical experience paper authors should prepend their paper title with ‘Practical:’ to provide clarity that this is a practical experience paper during the review process (this can be removed for the final camera-ready paper).

Practical experience papers are encouraged, but not required, to submit an artifact to the Artifact Evaluation process.

The selection criteria for papers in this category are:

• Originality: Papers should present CGO-related technologies applied to real-world problems with scope or characteristics that set them apart from previous solutions. Alternatively, papers may also report on scaling known techniques to significantly larger and/or more complex real-world problems.
• Foundations: Papers should incorporate the principles underpinning Code Generation and Optimization (CGO). However, a thorough discussion of theoretical foundations is not required; a summary of such should suffice.
• Insight: The practical experience should provide meaningful conclusions related to CGO topics that show unexpected or novel characteristics.
• Applicability: The results of the practical experience should be applicable beyond the specific system evaluated in the paper.

Geographic Diversity and Inclusion

Authors of papers accepted for CGO 2026 are encouraged to present their work in person. However, to foster the participation of students and professionals from everywhere, CGO 2026 will allow the remote presentation of papers, if their authors are unable to travel to the conference venue for reasons beyond their control (e.g. visa issues). Additionally, the conference organization will try to make attendance of CGO 2026 affordable for as many people as possible, with a specific focus on students from universities located in under-represented countries who are paper authors.

Artifact Evaluation

The Artifact Evaluation process is run by a separate committee whose task is to assess how the artifacts support the work described in the papers. This process contributes to improved reproducibility in research that should be a great concern to all of us. There is also some evidence that papers with a supporting artifact receive higher citations than papers without artifact evaluation. Authors of accepted papers at CGO have the option of submitting their artifacts for evaluation within two weeks of paper acceptance. To ease the organization of the AE committee, we kindly ask authors to indicate at the time they submit the paper, whether they are interested in submitting an artifact. Papers that go through the Artifact Evaluation process successfully will receive a seal of approval printed on the papers themselves. Additional information is available on the CGO AE web page. Authors of accepted papers are encouraged, but not required, to make these materials publicly available upon publication of the proceedings.

AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the IEEE Xplore Platform. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work.

CGO will make the proceedings freely available via the IEEE Xplore platform during the period from two weeks before to two weeks after the conference. This option will facilitate easy access to the proceedings by conference attendees, and it will also enable the community at large to experience the excitement of learning about the latest developments being presented in the period surrounding the event itself.

Distinguished Paper Awards

Up to 10% of papers accepted at CGO 2026 will be designated as Distinguished Papers, following the ACM policy. This award is open to both regular and tool papers.

Submission Site

Papers can be submitted for the second round at https://cgo26-second-round.hotcrp.com/ (the first-round link is https://cgo26-first-round.hotcrp.com/).

Submission Guidelines

Please make sure that your paper satisfies ALL of the following requirements before it is submitted:

• The paper must be original material that has not been previously published in another conference or journal, nor is currently under review by another conference or journal. Note that you may submit material presented previously at a workshop without copyrighted proceedings.

• Your submission is limited to ten (10) letter-size (8.5″x11″), single-spaced, double-column pages, using 10pt or larger font, not including references. There is no page limit for references. We strongly encourage the use of the IEEE Conference Template. Submissions not adhering to these submission guidelines may be outright rejected at the discretion of the program chairs. (Please make sure your paper prints satisfactorily on letter-size (8.5″x11″) paper: this is especially important for submissions from countries where A4 paper is standard.)

• Supplementary materials may be included as an Appendix at the end of the submitted paper. The Appendix has no page limit, but the text of the full paper excluding the Appendix must fit within 10 pages. Reviewers are not required to read the Appendix and may do so at their discretion. So papers must be self-contained without needing to read any material in the Appendix.

• Papers are to be submitted for double-blind review. Blind reviewing of papers will be done by the program committee, assisted by outside referees. Author names as well as hints of identity are to be removed from the submitted paper. Use care in naming your files. Source file names, e.g., Joe.Smith.dvi, are often embedded in the final output as readily accessible comments. In addition, do not omit references to provide anonymity, as this leaves the reviewer unable to grasp the context. Instead, if you are extending your own work, you need to reference and discuss the past work in third person, as if you were extending someone else’s research. We realize in doing this that for some papers it will still be obvious who the authors are. In this case, the submission will not be penalized as long as a concerted effort was made to reference and describe the relationship to the prior work as if you were extending someone else’s research. For example, if your name is Joe Smith:

  In previous work [1,2], Smith presented a new branch predictor for …. In this paper, we extend their work by …

  Bibliography

  [1] Joe Smith, “A Simple Branch Predictor for …,” Proceedings of CGO 2019.

  [2] Joe Smith, “A More Complicated Branch Predictor for…,” Proceedings of CGO 2019.

• Your submission must be formatted for black-and-white printers and not color printers. This is especially true for plots and graphs in the paper.

• Please make sure that the labels on your graphs are readable without the aid of a magnifying glass. Typically the default font sizes on the graph axes in a program like Microsoft Excel are too small.

• Please number the pages.

• To ease reviewing, please add line numbers to your submission. In LaTeX you can use the lineno package, with the ‘switch’ option.

• The paper must be written in English.

• The paper must be submitted in PDF. We cannot accept any other format, and we must be able to print the document just as we receive it. We strongly suggest that you use only the four widely-used printer fonts: Times, Helvetica, Courier and Symbol. Please make sure that the output has been formatted for printing on LETTER size paper. If generating the paper using “dvips”, use the option “-P cmz -t letter”, and if that is not supported, use “-t letter”.

• The Artifact Evaluation process is run by a separate committee whose task is to assess how the artifacts support the work described in the papers. Authors of accepted papers have the option of submitting their artifacts for evaluation within one week of paper acceptance. To ease the organization of the AE committee, we kindly ask authors to indicate at the time they submit the paper, whether they are interested in submitting an artifact. Papers that go through the Artifact Evaluation process successfully will receive a seal of approval printed on the papers themselves. Additional information is available on the CGO AE web page. Authors of accepted papers are encouraged, but not required, to make these materials publicly available upon publication of the proceedings.

Conflicts of Interest

Please read these guidelines on conflicts of interest carefully before submission.

• Authors must register all their conflicts on the paper submission site. Conflicts are needed to ensure appropriate assignment of reviewers. If a paper is found to have an undeclared conflict that causes a problem OR if a paper is found to declare false conflicts in order to abuse or “game” the review system, the paper may be rejected.

• Please declare a conflict of interest with the following people for any author of your paper:

  • Your Ph.D. advisor(s), post-doctoral advisor(s), Ph.D. students, and post-doctoral advisees, forever.
  • Family relations by blood or marriage, or their equivalent, forever (if they might be potential reviewers).
  • People with whom you have collaborated in the last FIVE years, including:
    • Co-authors of accepted/rejected/pending papers.
    • Co-PIs on accepted/rejected/pending grant proposals.
    • Funders (decision-makers) of your research grants, and researchers whom you fund.
  • People (including students) who shared your primary institution(s) in the last FIVE years.
  • Other relationships, such as close personal friendship, that you think might tend to affect your judgment or be seen as doing so by a reasonable person familiar with the relationship.
  • “Service” collaborations such as co-authoring a report for a professional organization, serving on a program committee, or co-presenting tutorials, do not themselves create a conflict of interest. Co-authoring a paper that is a compendium of various projects with no true collaboration among the projects does not constitute a conflict among the authors of the different projects.
  • Internships represent an institutional conflict during the time that the internship is active but not afterwards, unless another form of conflict exists (e.g. an on-going collaboration or co-authorship of a paper at any point during the previous FIVE years), in which case the conflict is no longer institutional but between individuals.
  • On the other hand, there may be others not covered by the above with whom you believe a COI exists, for example, an ongoing collaboration that has not yet resulted in the creation of a paper or proposal. Please report such COIs; however, you may be asked to justify them. Please be reasonable. For example, you cannot declare a COI with a reviewer just because that reviewer works on topics similar to or related to those in your paper. The PC Chairs may contact co-authors to explain a COI whose origin is unclear.
  • If in doubt, please contact the PC Chairs for advice on whether a conflict exists or not.