llvm dev - Jun 2013 - [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk

Hi,



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.



http://llvm.org/bugs/show_bug.cgi?id=16431



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.



Thanks,

-moh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130624/46543589/attachment.html>

Thanks for this work. This is really valuable.


On Mon, Jun 24, 2013 at 4:03 PM, moh <mohammad.r.haghighat at gmail.com>
wrote:
> - tests that cause infinite loops in the Clang optimizer
>
>
>
 Maybe you could collect a backtrace in the infinite loops to compare the
place in the optimizer where the bug is happening? That might help get a
rough idea of how many distinct bugs there are for this category.

-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130626/6c894110/attachment.html>