[icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk


I just submitted a bug report with a package containing 107 small test cases that fail on the latest LLVM/clang 3.4 main trunk (184563). Included are test sources, compilation commands, test input files, and results at –O0 and –O2 when applicable.


These tests have been automatically generated by an internal tool at Intel, the Intel Compiler fuzzer, icFuzz. The tests are typically very small. For example, for the following simple loop (test t5702) on MacOS X, clang at –O2 generates a binary that crashes:

// Test Loop Interchange

for (j = 2; j < 76; j++) {

for (jm = 1; jm < 30; jm++) {

h[j-1][jm-1] = j + 83;



The tests are put in to two categories

  • tests that have different runtime outputs when compiled at -O0 and -O2 (this category also includes runtime crashes)

  • tests that cause infinite loops in the Clang optimizer

Many of these failing tests could be due to the same bug, thus a much smaller number of root problems are expected.

Any help with triaging these bugs would be highly appreciated.