Latest Update

Follow Us on Social Media

Call for Contributions

Call for papers

23rd International Conference on Architectural Support for  Programming Languages and Operating Systems

PDF Version

Abstract submissions      Aug 4, 2017
Full paper submissions  Aug 11, 2017
Author response             Oct 25, 2017
Notification                        Nov 13, 2017
Final copy deadline         Jan 19, 2018


ASPLOS is the premier forum for multidisciplinary systems research spanning computer architecture and hardware, programming languages and compilers, operating systems and networking. The ASPLOS 2018 will be held in Williamsburg, Virginia, a town that combines a rich slice of American Colonial and Revolutionary history with a modern college atmosphere. Like its predecessors, ASPLOS 2018 invites papers on ground-breaking research at the intersection of at least two ASPLOS disciplines: architecture, programming languages, operating systems, and related areas. Non-traditional topics are especially encouraged. The importance of cross-cutting research continues to grow as we grapple with the end of Dennard scaling, the explosion of big data, scales ranging from ultra-low power wearable devices to exascale parallel and cloud computers, the need for sustainability, and increasingly human-centered applications. ASPLOS embraces systems research that directly targets these new problems in innovative ways. The research may target diverse goals, such as performance, energy and thermal efficiency, resiliency, security, and sustainability. The review process will be sensitive to the challenges of multidisciplinary work in emerging areas.


Areas of interest include, but are not limited to:

      • Existing and emerging platforms at all scales, from embedded to cloud
      • Internet services, cloud computing, and datacenters
      • Multicore architectures and systems
      • Heterogeneous architectures and accelerators
      • Systems for enabling parallelism at an extreme scale
      • Programming models, languages, and compilation for all platforms
      • Managing, storing, and computing on big data
      • Virtualization and virtualized systems
      • Memory and storage technologies and architectures
      • Power, energy, and thermal management
      • Security, reliability, and availability
      • Verification and testing, and their impact on design
      • Support for approximations and approximate computing
      • Non-traditional computing systems



Call for Workshops/Tutorials

PDF Version

Call for Tutorial Proposals

Tutorial proposals are solicited for ASPLOS-2018, which will take place in Williamsburg, VA. Tutorials will be held on March 24, 2018 (Saturday) and March 25, 2018 (Sunday).
Proposals for both half- and full-day tutorials are solicited on any topic that is relevant to the ASPLOS audience. In previous years, tutorials seeking to achieve either of the following goals have been particularly successful:
Describe an important piece of research infrastructure.
Educate the community on an emerging topic.

Submission Procedures
Proposals should provide the following information:
Presenter(s) and contact information.
Proposed duration (full day, half day).
1-2 paragraph abstract suitable for tutorial publicity.
1 paragraph biography per presenter suitable for tutorial publicity.
1-3 page description (for evaluation). This should include:
Tutorial scope and objectives,
Topics to be covered,
Target audience,
If the tutorial has been held previously, the location (i.e., conference), date, and number of attendees.

Proposals should be submitted in PDF format via e-mail to Zhijia Zhao ( ) and Rajiv Gupta ( with the subject “ASPLOS2018 Tutorial Proposal”. Submissions will be acknowledged via e-mail.

Important Dates
Submission deadline: Monday, November 3, 2017
Notification:Monday, November 24th 2017



Call for Workshop Proposals

Workshop and tutorial proposals are solicited for ASPLOS-2018, Williamsburg, VA. Workshops will be held on March 24, 2018 (Saturday) and March 25, 2018 (Sunday).

Proposals in the interplay between programming languages, computer architecture, operating systems, and user interfaces to deal with power, performance, resilience, and programmer productivity issues in emerging areas such as datacenters and cloud computing, systems based on non-volatile memory technologies, large scale data analysis, smart infrastructure, and extreme scale computing are encouraged.

Please include in your proposal
Title of the workshop
Organizers and their affiliations
Sample call for papers
Duration – Half-Day or Full Day
Preferred Day – Saturday or Sunday
If the workshop was previously held, the location (conference), date, and number of attendees

Proposals should be submitted via e-mail to Zhijia Zhao ( and Rajiv Gupta ( with the subject “ASPLOS2018 Workshop Proposal”. Submissions will be acknowledged via e-mail.
Feel free to contact Zhijia and Rajiv if you have any questions about the suitability of a workshop for ASPLOS or for any other related matters.

Important Dates
Submission deadline: Monday, November 3, 2017
Notification:Monday, November 24th 2017



Call for Shadow PC Participation

23rd International Conference on Architectural Support for Programming Languages and Operating Systems

PDF Version

ASPLOS is organizing a shadow program committee for ASPLOS 2018. If you are interested in participating, please send an email to the shadow PC organizers: Johann Hauswald (University of Michigan, jahausw AT and Yunqi Zhang (University of Michigan, yunqi AT before July 31st, 2017. Please include a short paragraph describing your current research, areas of expertise, and publications: this will help us with selecting candidates and assigning papers for review. Feel free to reach out should you have any questions.


Being on a shadow PC is an excellent opportunity for systems researchers (PhD students, post-docs and new faculty members) to get experience in community service, i.e., program committee practices.

Shadow PC members are expected to write their own detailed and rigorous reviews for their assigned papers. We expect a review load of 15-20 papers per member. Members especially are also expected to attend a one-day shadow PC meeting in person which will coincide with the official PC meeting location (Chicago or Atlanta) and date. The reviews from the shadow PC will not impact the decisions of the main conference PC. Shadow PC co-chairs (Prof. Lingjia Tang and Prof. Thomas Wenisch) will lead the discussions at the shadow PC meeting, and other members of the main conference PC will also be invited to the meeting, making this an invaluable learning experience for the shadow PC members.

The ASPLOS shadow PC will follow the same timeline as the main PC ( We plan to have the shadow PC meeting a day after the conference PC meeting (November 11th, 2017).

Being a member of a shadow PC is a lot of work but also a great learning experience for a number of reasons:

  • Getting to know how a PC is run and how it operates.
  • Seeing how more experienced reviewers judge the same papers that you review.
  • Getting to see both strong and weak papers at the submission stage.
  • Submitting high quality reviews makes one a possible candidate for future PCs.
  • Discussing the papers with ASPLOS main PC members who will attend the shadow meeting.

Important Dates

  • Deadline to apply for shadow PC: July 31st, 2017
  • Shadow PC meeting: November 11th, 2017

Shadow PC Co-Chairs

  • Lingjia Tang, University of Michigan
  • Thomas Wenisch, University of Michigan


  • Johann Hauswald, University of Michigan
  • Yunqi Zhang, University of Michigan



23rd ACM International Conference on Architectural Support for Programming Languages and Operating Systems
Williamsburg, VA, U.S.A, March, 2018

This document provides instructions for submitting papers to the 23rd International Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS), 2018. In an effort to respect the efforts of reviewers and in the interest of fairness to all prospective authors, we request that all submissions to ASPLOS 2018 follow the formatting and submission rules detailed below. Submissions that violate these instructions may not be reviewed, at the discretion of the program chair, in order to maintain a review process that is fair to all potential authors. An example submission (formatted using the ASPLOS’18 submission format) that contains the submission and formatting guidelines can be downloaded from here: Sample PDF. The content of the document mirrors the submission instructions on this page.

Submission Site:

Please follow this link to submit your paper.
Abstract/paper registration deadline:
Aug 4, 2017 (11:59:59pm US eastern time)

Full paper submission deadline:
Aug 11, 2017 (11:59:59pm US eastern time)


  • Paper must be submitted in printable PDF format.
  • Text must be in a minimum 10pt (not 9pt) font.
  • Paper must be at most 11 pages, including any appendix, but not including references.
  • No page limit for references.
  • Each reference must specify all authors (no et al.).
  • Authors of all accepted papers will be required to give a lightning presentation (about 90s) and a poster in addition to the regular conference talk.
  • Proceedings will appear in the ACM digital library up to two weeks before the conference.

Paper Evaluation Objectives:

The committee will make every effort to judge each submitted paper on its own merits. There will be no target acceptance rate. We expect to accept a wide range of papers with appropriate expectations for evaluation — while papers that build on significant past work with strong evaluations are valuable, papers that open new areas with less rigorous evaluation are equally welcome and especially encouraged. Given the wide range of topics covered by ASPLOS, every effort will be made to find expert reviewers.

Paper Preparation Instructions

Paper Formatting

Papers must be submitted in printable PDF format and should contain a maximum of 11 pages of single-spaced two-column text, not including references. You may include any number of pages for references, but see below for more instructions. If you are using LATEX to typeset your paper, then we suggest that you use the template here: LATEX Template. (This sample PDF was prepared with that template.) If you are using a different software package to typeset your paper, then please adhere to the guidelines given in Table 1.

One exception is that authors may use the SIGPLAN style/class file here, but only with the 10pt body font option (9pt will be rejected) and modified as needed for the requirements of the references section below. This is marginally different from the specified template, but will be accepted due to its widespread use.

Please ensure that you include page numbers with your submission. This makes it easier for the reviewers to refer to different parts of your paper when they provide comments. Please ensure that your submission has a banner at the top of the title page, similar to this one, which contains the submission number and the notice of confidentiality. If using the template, just replace XXX with your submission number.

Table 1: Formatting guidelines for submission.
Field Value
File format PDF
Page limit 11 pages, not including references
Paper size US Letter 8.5in x 11in
Top margin 1in
Bottom margin 1in
Left margin 0.75in
Right margin 0.75in
Body 2-column, single-spaced
Separation between columns 0.25in
Body font 10pt
Abstract font 10pt, italicized
Section heading font 12pt, bold
Subsection heading font 10pt, bold
Caption font 9pt, bold
References 8pt, no page limit, list all authors’ names


Author List. Reviewing will be double blind; therefore, please do not include any author names on any submitted documents except in the space provided on the submission form. You must also ensure that the metadata included in the PDF does not give away the authors. If you are improving upon your prior work, refer to your prior work in the third person and include a full citation for the work in the bibliography. For example, if you are building on your own prior work in the papers [2, 3, 4], you would say something like: “While the authors of [2, 3, 4] did X, Y, and Z, this paper additionally does W, and is therefore much better.” Do NOT omit or anonymize references for blind review. There is one exception to this for your own prior work that appeared in IEEE CAL, workshops without archived proceedings, etc. as discussed later in this document.

Figures and Tables. Ensure that the figures and tables are legible. Please also ensure that you refer to your figures in the main text. Many reviewers print the papers in gray-scale. Therefore, if you use colors for your figures, ensure that the different colors are highly distinguishable in gray-scale.

References. There is no length limit for references. Each reference must explicitly list all authors of the paper. Papers not meeting this requirement will be rejected. Authors of NSF proposals should be familiar with this requirement. Knowing all authors of related work will help find the best reviewers. Since there is no length limit for the number of pages used for references, there is no need to save space here.

Paper Submission Instructions

Declaring Authors

Declare all the authors of the paper upfront. Addition/removal of authors once the paper is accepted will have to be approved by the program chair, since it potentially undermines the goal of eliminating conflicts for reviewer assignment.

Areas and Topics

ASPLOS emphasizes multidisciplinary research. Submissions should ideally emphasize synergy of two or more ASPLOS areas: architecture, programming languages, operating systems, and related areas (broadly interpreted). Authors should indicate these areas on the submission form as well as specific topics covered by the paper for optimal reviewer match. If you are unsure whether your paper falls within the scope of ASPLOS, please check with the program chair – ASPLOS is a broad, multidisciplinary conference and encourages new topics.

Declaring Conflicts of Interest

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 (COI) with the following 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 of 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.

“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. On the other hand, there may be others not covered by the above with whom you believe a COI exists, for example, close personal friends. 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 Chair may contact co-authors to explain a COI whose origin is unclear. We hope to draw most reviewers from the PC and the ERC, but others from the community may also write reviews. Please declare all your conflicts (not just restricted to the PC and ERC). When in doubt, contact the program chair.

Concurrent Submissions and Workshops

By submitting a manuscript to ASPLOS’18, the authors guarantee that the manuscript has not been previously published or accepted for publication in a substantially similar form in any conference, journal, or workshop. The only exceptions are (1) workshops without archived proceedings such as in the ACM digital library (or where the authors chose not to have their paper appear in the archived proceedings), or (2) venues, such as IEEE CAL, where there is an explicit policy that such publication does not preclude longer conference submissions. These are not considered prior publications.  Technical reports and papers posted on public social media sites, Web pages, or online repositories, such as, are not considered prior publications either. In such exceptional cases, the submitted manuscript may ignore the above work to preserve author anonymity. This information must, however, be provided on the submission form – the program chair(s) will make this information available to reviewers if it becomes necessary to ensure a fair review. (This policy will be explicitly conveyed to the reviewers as well.)  The authors also guarantee that no paper that contains significant overlap with the contributions of the submitted paper will be under review for any other conference, journal, or workshop during the ASPLOS’18 review period. Violation of any of these conditions will lead to rejection.  As always, if you are in doubt, it is best to contact the program chair(s).  Finally, we also note that the ACM Plagiarism Policy ( covers a range of ethical issues concerning the misrepresentation of other works or one’s own work.

Early Access in the Digital Library

The ASPLOS’18 proceedings will be freely available via the ACM Digital Library for up to two weeks before and up to a month after the conference. Authors must consider any implications of this early disclosure of their work before submitting their papers.


Several ideas in this document and parts of the text have been taken from previous conferences, so we thank their program chairs.  In particular, John Carter (ASPLOS’17), Yuanyuan Zhou (ASPLOS’16), Sandhya Dwarkadas (ASPLOS’15), Sarita Adve (ASPLOS’14), Steve Keckler (ISCA’14), Christos Kozyrakis (MICRO’13), Margaret Martonosi (ISCA’13), Onur Mutlu (MICRO’12), and Michael L. Scott (ASPLOS’12)

Example References

[1] Leslie Lamport. LATEX: A Document Preparation System. Addison-Wesley, Reading, Massachusetts, 2nd Edition, 1994.

[2] Firstname1 Lastname1 and Firstname2 Lastname2. A very nice paper to cite. In Proceedings of the 33rd Annual ACM SIGPLAN Conference on Programming Language Design and Implementation, 2012.

[3] Firstname1 Lastname1, Firstname2 Lastname2, and Firstname3 Lastname3. Another very nice paper to cite. In Proceedings of the 22nd ACM Symposium on Operating Systems Principles, 2011.

[4] Firstname1 Lastname1, Firstname2 Lastname2, Firstname3 Lastname3, Firstname4 Lastname4, and Firstname5 Lastname5. Yet another very nice paper to cite, with many author names all spelled out. In Proceedings of the 38th Annual International Symposium on Computer Architecture, 2011.



Organization Committee

General Chairs Xipeng Shen North Carolina State University
  James Tuck North Carolina State University
Program Chairs Ricardo Bianchini Microsoft Research
  Vivek Sarkar Rice University
Local Arrangements Chair Adwait Jog College of William and Mary
  Xu Liu College of William and Mary
Finance Guoliang Jin North Carolina State University
Workshop & Tutorial Rajiv Gupta University of California, Riverside
  Zhijia Zhao University of California, Riverside
Travel Grant John Criswell University of Rochester
  Ulya Karpuzcu University of Minnesota
ACM SRC and Posters Shuaiwen (Leon) Song Pacific Nortwest National Lab.
Wild and Crazy Ideas Michael Carbin Massachusetts Institute of Technology
  Luis Ceze University of Washington
Lightning Session Zheng Zhang Rutgers University
Registration Ardalan Amiri Sani University of California, Irvine
  Jun Yang University of Pittsburgh)
Publicity Boris Grot University of Edinburgh
  Gennady Pekhimenko Microsoft Research and University of Toronto
  Jidong Zhai Tsinghua University, China
  Hyesoon Kim Georgia Tech
Submission Bo Wu Colorado School of Mines
Web Xuehai Qian University of Southern California
  Hung-Wei Tseng North Carolina State University
Sponsor Yungang Bao Chinese Academy of Sciences
  Rudolf Eigenmann Purdue University
  Grigori Fursin Dividiti Co.
  Robert Hundt Google
Publication Felix Xiaozhu Lin Purdue University
  George Patsilaras Qualcomm Co.

Program Committee

Yungang Bao China ICT
Rajkishore Barik Intel Labs
Andrew Baumann Microsoft Research
Abhishek  Bhattacharjee Rutgers University
Ricardo Bianchini Microsoft Research
Uday Bondhugula Indian Institute of Science
Adrian Caulfield Microsoft Research
Luis Ceze University of Washington
Rong Chen Shanghai Jiao Tong University
Fred Chong University of Chicago
Christina Delimitrou Cornell University
Chen Ding University of Rochester
Natalie Enright Jerger University of Toronto
Phillip Gibbons Carnegie Mellon University
David Grove IBM Research
Rajiv Gupta University of California at Riverside
Tim Harris Oracle
Hank Hoffman University of Chicago
Trent Jaeger Penn State University
Mahmut Kandemir Penn State University
Kim Keeton Hewlett-Packard Enterprise
Martha Kim Columbia University
Seyong Lee Oak Ridge National Lab
Xu Liu College of William & Mary
Jean-Pierre Lozi University of Nice Sophia Antipolis
Shan Lu University of Chicago
Scott Mahlke University of Michigan at Ann Arbor
Kathryn S. McKinley Google
Satish Narayanasamy University of Michigan at Ann Arbor
David Nellans Nvidia
Jason Nieh Columbia University
Santosh Pande Georgia Tech
Keshav Pingali University of Texas at Austin
Vivien Quema Grenoble INP
Vijay Reddi University of Texas at Austin
Christopher J. Rossbach University of Texas at Austin and VMware Research Group
Karu Sankaralingam University of Wisconsin at Madison
Vivek Sarkar Georgia Tech
Kai Shen Google
Arrvindh Shriraman Simon-Fraser University
Mark Silberstein Technion
Armando Solar-Lezama Massachusetts Institute of Technology
Yan Solihin North Carolina State University
Karin Strauss Microsoft Research
Jeff Stuecheli IBM
Michael Swift University of Wisconsin at Madison
Lingjia Tang University of Michigan at Ann Arbor
Mohit Tiwari University of Texas at Austin
Dan Tsafrir Technion and VMware Research Group
Haris Volos Hewlett-Packard Enterprise
Thomas Wenisch University of Michigan at Ann Arbor
Yiying Zhang Purdue University

External Review Committee

David August Princeton University
Rajeev Balasubramonian University of Utah
Christopher Batten Cornell University
Suparna Bhattacharya Hewlett-Packard Enterprise
Steve Blackburn Australian National University
Michael Bond Ohio State University
John Carter IBM Research
Brad Chamberlain Cray
Evan Chang University of Colorado at Boulder
Wenguang Chen Tsinghua University
Yunji Chen ICT-Chinese Academy of Sciences
John Criswell University of Rochester
Chita Das Penn  State University
Reetuparna Das University of Michigan at Ann Arbor
Qingyuan Deng Facebook
Mattan Erez University of Texas at Austin
Michael Factor IBM Research
Sasha Fedorova University of British Columbia
Jayneel Gandhi VMware Research Group
Ada Gavrilovska Georgia Tech
Inigo Goiri Microsoft Research
Ganesh  Golapakrishnan University of Utah
K. Gopinath Indian Institute of Science (IISc)
Boris Grot University of Edinburgh
Qi Guo ICT-Chinese Academy of Sciences
Steven Hand Google
Akihiro Hayashi Rice University
Matthew Hicks Virginia Tech
Yu Hua Huazhong University of Science and Technology
Jeff Huang Texas A&M University
Wen-mei Hwu University of Illinois at Urbana-Champaign
Samira Kahn University of Virginia
Baris Kasikci University of Michigan at Ann Arbor
Jangwoo Kim Seoul National University
Uli Kremer Rutgers University
Orran Krieger Boston University
James Larus EPFL
Julia Lawall INRIA
Doug Lea SUNY Oswego
Ben Lee Duke University
Dongyoon Lee Virginia Tech
Chao Li Qualcomm
Cong Liu University of Texas at Dallas
Lei Liu ICT-Chinese Academy of Sciences
Andrew Lumsdaine Indiana University and PNNL
Daniel Lustig Nvidia
Virendra Marathe Oracle
Madan Musuvathi Microsoft Research
Onur Mutlu ETH Zurich
Santosh Nagarakatte Rutgers University
Thu D. Nguyen Rutgers University
Li-Shiuan Peh National University of Singapore
Don Porter University of North Carolina at Chapel Hill
Louis-Noel Pouchet Colorado State University
Shaz Qadeer Microsoft Research
Xuehai Qian University of Southern California
John Regehr University of Utah
Steve  Reinhardt Microsoft
Martin Rinard Massachusetts Institute of Technology
Amitabha Roy Intel Labs
Adrian Sampson Cornell University
Joshua San Miguel University of Toronto
Jennifer Sartor Vrije Universiteit Brussel
Koushik Sen University of California at Berkeley
Tim Sherwood University of California at Santa Barbara
Anand Sivasubramaniam Penn State University
Ben Titzer Google
Josep Torrellas University of Illinois at Urbana-Champaign
David Wentzlaff Princeton University
Guoqing (Harry) Xu University of California at Irvine
Ding Yuan University of Toronto
Antonia Zhai University of Minnesota