The LLVM Compiler Infrastructure
Site Map:
Download!
Download now: LLVM 7.0.0
All Releases
APT Packages
Win Installer

View the open-source
license

Search this Site


Useful Links
Release Emails
7.0.0: Sep 2018
6.0.1: July 2018
5.0.2: May 2018
6.0.0: Mar 2018
5.0.1: Dec 2017
5.0.0: Sep 2017
4.0.1: Jul 2017
4.0.0: Mar 2017
3.9.1: Dec 2016
3.9.0: Sep 2016
3.8.1: July 2016
3.8.0: Mar 2016
3.7.1: Jan 2016
3.7.0: Sep 2015
3.6.2: Jul 2015
3.6.1: May 2015
3.5.2: Apr 2015
3.6: Feb 2015
3.5.1: Jan 2015
3.5: Sep 2014
3.4.2: June 2014
3.4.1: May 2014
3.4: Jan 2014
3.3: Jun 2013
3.2: Dec 2012
3.1: May 2012
3.0: Dec 2011
2.9: Apr 2011
2.8: Oct 2010
2.7: Apr 2010
2.6: Oct 2009
2.5: Mar 2009
2.4: Nov 2008
2.3: Jun 2008
2.2: Feb 2008
2.1: Sep 2007
2.0: May 2007
Older News

Maintained by the
llvm-admin team
EuroLLVM'19 Developers' Meeting

  1. Conference Home Page
  • Conference Dates: April 8-9, 2019
  • Location: Brussels, Belgium
Call for Papers - Detailed guidance on writing a proposal for the LLVM developers' meeting

This is a guide to help you submit the best proposal and increase your chances of your proposal being accepted. The LLVM Developers' Meeting program committee receives more proposals than can be accepted, so please read this guide carefully.

If you have never presented at an LLVM Developers' Meeting, then do not fear this process. We are actively looking for new speakers who are excited about LLVM and helping grow the community through these educational talks! You do not need to be a long time developer to submit a proposal.

General guidelines:

  • It should be clear from your abstract what your topic is, who your targeted audience is, and what are the takeaways for attendees. The program committee gets a lot of proposals and does not have time to read 10 page papers for each submission (excluding SRC submissions).
  • Talks about a use of LLVM (etc) should include details about how LLVM is used and not only be about the resulting application.
  • Tutorials on "how to use X" in LLVM (or other subproject) are greatly desired and beneficial to many developers. Entry level topics are encouraged as well.
  • Talks that have been presented at other technical conferences tend to not get accepted. If you have presented this topic before, make it clear what is new and different in your talk.
  • We suggest you proofread and pay attention to grammar.

Technical talk & tutorial proposal template:

Title:

  • This will be displayed on the website, schedule, and signs.
  • Keep it short and catchy to attract attendees to your talk. A couple of examples are "WebAssembly: Here Be Dragons" or "Beyond Sanitizers: guided fuzzing and security hardening".

Speaker Name(s), Company, Email:

  • This should be only the people giving the talk. HotCRP allows you to list authors but not speakers. We also recommend you put speakers only in the HotCRP "Contact" field so they are the ones contacted regarding conference details.

Abstract:

  • 1-2 paragraphs. Keep in mind that this is displayed on the schedule and website for attendees to consider when selecting talks.

Submission:

  • Include details about your talk in the PDF you upload: an outline, demo description, background of the speaker, etc.
  • For tutorials, include additional details such as tutorial outline, what materials you will provide attendees, etc.
  • This will not be published and is intended for the PC to better understand how interesting your talk will be to the audience. For example, if you would prefer not to reveal some conclusions in the published abstract, explaining them here ensures that the PC can take them into account when evaluating your proposal.

SRC talk proposal template:

Title:

  • This will be displayed on the website, schedule, and signs.
  • Keep it short and catchy to attract attendees to your talks. A couple of examples are "WebAssembly: Here Be Dragons" or "Beyond Sanitizers: guided fuzzing and security hardening".

Speaker Name(s), Company, Email:

  • This should be only the people giving the talk. HotCRP allows you to list authors but not speakers. We also recommend you put speakers only in the HotCRP "Contact" field so they are the ones contacted regarding conference details.

Abstract:

  • 1-2 paragraphs. Keep in mind that this is displayed on the schedule and website for attendees to consider when selecting talks.

Submission:

  • Details must be provided in a 2 pages pdf, formatted using the SIGPLAN article format : 8.5in x 11in single spaced, double column page with a 10pt or larger font.
  • Optionally, you can attach your actual research paper, but that's mainly for the benefit of the reviewers who may not have time to actually read it.
  • If you need an embargo (delaying the publishing of the slides and video by up to 12 months), please fill-in the embargo request text box.
  • You are strongly encouraged to submit your talk as a poster as well as it will enable wider discussions at the meeting. The Program committee might also not select your talk proposal, but still offers you to present a poster.
  • This will not be published and is intended for the PC to better understand how interesting your talk will be to the audience. For example, if you would prefer not to reveal some conclusions in the published abstract, explaining them here ensures that the PC can take them into account when evaluating your proposal.

BoF proposal template:

Title:

  • This will be displayed on the website, schedule, and signs. These tend to be very straight forward about the area being discussed. An example is "Future directions and features for LLDB".

Speaker Name(s), Company, Email:

  • This should be only the people giving the talk. HotCRP allows you to list authors but not speakers. We also recommend you put speakers only in the HotCRP "Contact" field so they are the ones contacted regarding conference details.

Abstract:

  • 1-2 paragraphs. Keep in mind that this is displayed on the schedule and website for attendees to consider when selecting which BoFs to attend.

Submission:

  • Provide additional details in the PDF you upload: goals of the BoF, presentation style. BoFs are to brainstorm ideas on a specific topic but you will be more successful if you have a guided discussion with talking points and actionable items at the end.
  • Provide some talking points or potential subtopics.
  • This will not be published and is intended for the PC to better understand how interesting your talk will be to the audience.

Lightning talks & Poster proposal template:

Title:

  • This will be displayed on the website, schedule, and signs.
  • Keep it short and catchy to attract attendees to your talks. A couple of examples are "WebAssembly: Here Be Dragons" or "Beyond Sanitizers: guided fuzzing and security hardening".

Speaker Name(s), Company, Email:

  • This should be only the people presenting the poster. HotCRP allows you to list authors but not presenters. We also recommend you put presenters only in the HotCRP "Contact" field so they are the ones contacted regarding conference details.

Abstract:

  • 1-2 paragraphs. Keep in mind that this is displayed on the schedule and website for attendees to consider when selecting the posters they want to look at.

Submission:

  • No need for a detailed PDF submission.

Diamond Sponsors:

Platinum Sponsors:

Gold Sponsors:

Silver Sponsors:

Thank you to our sponsors!