LLVM welcomes contributions of all kinds. To get started, please review the following topics:
Contributing DeveloperPolicy CodeReview SupportPolicy SphinxQuickstartTemplate Phabricator HowToSubmitABug BugLifeCycle CodingStandards GitBisecting GitRepositoryPolicy
ContributingAn overview on how to contribute to LLVM.
DeveloperPolicyThe LLVM project's policy towards developers and their contributions.
CodeReviewThe LLVM project's code-review process.
SupportPolicyThe LLVM support policy for core and non-core components.
SphinxQuickstartTemplateA template + tutorial for writing new Sphinx documentation. It is meant to be read in source form.
PhabricatorDescribes how to use the Phabricator code review tool hosted on http://reviews.llvm.org/ and its command line interface, Arcanist.
HowToSubmitABugInstructions for properly submitting information about any bugs you run into in the LLVM system.
BugLifeCycleDescribes how bugs are reported, triaged and closed.
CodingStandardsDetails the LLVM coding standards and provides useful information on writing efficient C++ code.
GitBisectingDescribes how to use
git bisecton LLVM's repository.GitRepositoryPolicyCollection of policies around the git repositories.
Information about LLVM's development process.
Projects HowToReleaseLLVM Packaging ReleaseProcess HowToAddABuilder ReleaseNotes
ProjectsHow-to guide and templates for new projects that use the LLVM infrastructure. The templates (directory organization, Makefiles, and test tree) allow the project code to be located outside (or inside) the
llvm/tree, while using LLVM header files and libraries.HowToReleaseLLVMThis is a guide to preparing LLVM releases. Most developers can ignore it.
ReleaseProcessThis is a guide to validate a new release, during the release process. Most developers can ignore it.
HowToAddABuilderInstructions for adding new builder to LLVM buildbot master.
PackagingAdvice on packaging LLVM into a distribution.
Release notes for the current release <ReleaseNotes>This describes new features, known bugs, and other limitations.
If you can't find what you need in these docs, try consulting the mailing lists. In addition to the traditional mailing lists there is also a Discourse server available.
- Developer's List (llvm-dev)__
This list is for people who want to be included in technical discussions of LLVM. People post to this list when they have questions about writing code for or using the LLVM tools. It is relatively low volume.
- Commits Archive (llvm-commits)__
This list contains all commit messages that are made when LLVM developers commit code changes to the repository. It also serves as a forum for patch review (i.e. send patches here). It is useful for those who want to stay on the bleeding edge of LLVM development. This list is very high volume.
- Bugs & Patches Archive (llvm-bugs)__
This list gets emailed every time a bug is opened and closed. It is higher volume than the LLVM-dev list.
- Test Results Archive (llvm-testresults)__
A message is automatically sent to this list by every active nightly tester when it completes. As such, this list gets email several times each day, making it a high volume list.
- LLVM Announcements List (llvm-announce)__
This is a low volume list that provides important announcements regarding LLVM. It gets email about once a month.
A number of regular calls are organized on specific topics. It should be expected that the range of topics will change over time. At the time of writing, the following sync-ups are organized:
LLVM regular sync-up calls| Topic | Frequency | Calendar link | Minutes/docs link |
|---|---|---|---|
| Loop Optimization Working Group | Every 2 weeks on Wednesday | Minutes/docs | |
| RISC-V | Every 2 weeks on Thursday | ics gcal | |
| Scalable Vectors and Arm SVE | Monthly, every 3rd Tuesday | ics gcal | Minutes/docs |
| ML Guided Compiler Optimizations | Monthly | Minutes/docs | |
| LLVM security group | Monthly, every 3rd Tuesday | ics gcal | Minutes/docs |
| CIRCT | Weekly, on Wednesday | Minutes/docs | |
| MLIR design meetings | Weekly, on Thursdays | Minutes/docs | |
| flang | Multiple meeting series, documented here | ||
| OpenMP | Multiple meeting series, documented here | ||
| LLVM Alias Analysis | Every 4 weeks on Tuesdays | ics | Minutes/docs |
| Windows/COFF related developments | Every 2 months on Thursday | Minutes/docs | |
| Vector Predication | Every 2 weeks on Tuesdays, 3pm UTC | Minutes/docs | |
| LLVM Pointer Authentication | Every month on Mondays | ics | Minutes/docs |
| MemorySSA in LLVM | Every 8 weeks on Mondays | ics gcal | Minutes/docs |
| LLVM Embedded Toolchains | Every 4 weeks on Thursdays | ics gcal | Minutes/docs |
A number of experienced LLVM contributors make themselves available for a chat on a regular schedule, to anyone who is looking for some guidance. Please find the list of who is available when, through which medium, and what their area of expertise is. Don't by shy to dial in!
Of course, people take time off from time to time, so if you dial in and you don't find anyone present, chances are they happen to be off that day.
LLVM office hours| Name | In-scope topics | When? | Where? | Languages |
|---|---|---|---|---|
| Kristof Beyls | General questions on how to contribute to LLVM; organizing meetups; submitting talks; and other general LLVM-related topics. Arm/AArch64 codegen. | Every 2nd and 4th Wednesday of the month at 9.30am CET, for 30 minutes. ics | Jitsi | English, Flemish, Dutch |
Users and developers of the LLVM project (including subprojects such as Clang) can be found in #llvm on irc.oftc.net.
This channel has several bots.
- Buildbot reporters
- llvmbb - Bot for the main LLVM buildbot master. http://lab.llvm.org/buildbot/#/console
- robot - Bugzilla linker. %bug <number>
- clang-bot - A geordi instance running near-trunk clang instead of gcc.
In addition to the traditional IRC there is a Discord chat server available. To sign up, please use this invitation link.
MeetupGuidelines
Besides developer meetings and conferences, there are several user groups called LLVM Socials. We greatly encourage you to join one in your city. Or start a new one if there is none:
MeetupGuidelines
Proposals for massive changes in how the community behaves and how the work flow can be better.
CodeOfConduct Proposals/GitHubMove BugpointRedesign Proposals/TestSuite Proposals/VariableNames Proposals/VectorizationPlan Proposals/VectorPredication
CodeOfConductProposal to adopt a code of conduct on the LLVM social spaces (lists, events, IRC, etc).
Proposals/GitHubMoveProposal to move from SVN/Git to GitHub.
BugpointRedesignDesign doc for a redesign of the Bugpoint tool.
Proposals/TestSuiteProposals for additional benchmarks/programs for llvm's test-suite.
Proposals/VariableNamesProposal to change the variable names coding standard.
Proposals/VectorizationPlanProposal to model the process and upgrade the infrastructure of LLVM's Loop Vectorizer.
Proposals/VectorPredicationProposal for predicated vector instructions in LLVM.