How to submit an LLVM bug report

If you're working with LLVM and run into a bug, we definitely want to know +about it. This document describes what you can do to increase the odds of +getting it fixed quickly.

+ +

Basically you have to do two things at a minimum. First, decide whether the +bug crashes the compiler (or an LLVM pass), or if the compiler is miscompiling the program. Based on what type of bug it is, follow the instructions in the linked section to narrow down the bug so that the person who fixes it will be able to find the problem -more easily.

- -Once you have a reduced test-case, go to - -the LLVM Bug Tracking System, - -select the catagory in which the bug falls, and fill out the form with the -necessary details. The bug description should contain the following -information: +more easily.

+ +

Once you have a reduced test-case, go to the LLVM Bug Tracking +System, select the category in which the bug falls, and fill out the form +with the necessary details. The bug description should contain the following +information:

All information necessary to reproduce the problem.
The reduced test-case that triggers the bug.

-Thanks for helping us make LLVM better!

Thanks for helping us make LLVM better!

-Crashing Bugs -

+ Crashing Bugs +

+ +

More often than not, bugs in the compiler cause it to crash - often due to an assertion failure of some sort. If you are running opt or analyze directly, and something crashes, jump to the section on bugs in LLVM passes. Otherwise, the most important piece of the puzzle is to figure out if it is the GCC-based front-end that is -buggy or if it's one of the LLVM tools that has problems.

+buggy or if it's one of the LLVM tools that has problems.

-To figure out which program is crashing (the front-end, gccas, -or gccld), run the llvm-gcc command line as you -were when the crash occurred, but add a -v option to the command line. -The compiler will print out a bunch of stuff, and should end with telling you -that one of cc1, gccas, or gccld -crashed.

To figure out which program is crashing (the front-end, +gccas, or gccld), run the +llvm-gcc command line as you were when the crash occurred, but +add a -v option to the command line. The compiler will print out a +bunch of stuff, and should end with telling you that one of cc1, +gccas, or gccld crashed.

If cc1 crashed, you found a problem with the front-end. -Jump ahead to the section on front-end bugs. -
If gccas crashed, you found a bug in one of -the passes in gccas. -
If gccld crashed, you found a bug in one -of the passes in gccld. -
Otherwise, something really weird happened. Email the list with what you -have at this point. -

If cc1 crashed, you found a problem with the front-end. + Jump ahead to the section on front-end bugs.

+ +

If gccas crashed, you found a bug in one + of the passes in gccas.

+ +

If gccld crashed, you found a bug in one + of the passes in gccld.

+ +

Otherwise, something really weird happened. Email the list with what you + have at this point.

+ +