search for: icfuzz

...vm.org/bugs/show_bug.cgi?id=16431 I expect that these failures correspond to 2+ unique bugs. Cheers, -moh -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Thursday, January 09, 2014 6:01 AM To: Haghighat, Mohammad R Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk ----- Original Message ----- > From: "Hal Finkel" <hfinkel at anl.gov> > To: "Mohammad R Haghighat" <mohammad.r.haghighat at intel.com> > Cc: llvmdev at cs.uiuc.edu > Sent:...

...s, > -moh > > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu > [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Haghighat, > Mohammad R > Sent: Friday, July 26, 2013 8:19 PM > To: Hal Finkel > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly > generated tests that fail on clang 3.4 trunk > > Hal, > > I ran the failing tests in the attachment to the bug 16431 on the > latest clang trunk (version 3.4 trunk 187225). > http://llvm.org/bugs/show_bug.cgi?id=16431 > > The foll...

...4 trunk 187225). http://llvm.org/bugs/show_bug.cgi?id=16431 The following tests still fail: Tests in diff: t10236 t12206 t2581 t6734 t7788 t7820 t8069 t9982 All tests in InfLoopInClang: t19193 t22300 t25903 t27872 t33143 t8543 Meanwhile, I'll launch a new run of icFuzz and will post the results later. -moh -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Friday, July 26, 2013 8:33 AM To: Haghighat, Mohammad R Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on...

----- Original Message ----- > Great job, Hal! > > Sure. I'd be happy to run icFuzz and report the fails once these bugs > are fixed and thereafter whenever people want new runs. Obviously, > this can be automated, but the problem is that icFuzz is not > currently open sourced. I would be happy to see this open sourced, but I think that we can work something out regardle...

...me as before or could actually be new bugs. Cheers, -moh -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Haghighat, Mohammad R Sent: Friday, July 26, 2013 8:19 PM To: Hal Finkel Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk Hal, I ran the failing tests in the attachment to the bug 16431 on the latest clang trunk (version 3.4 trunk 187225). http://llvm.org/bugs/show_bug.cgi?id=16431 The following tests still fail: Tests i...

Great job, Hal! Sure. I'd be happy to run icFuzz and report the fails once these bugs are fixed and thereafter whenever people want new runs. Obviously, this can be automated, but the problem is that icFuzz is not currently open sourced. Once there's a bug in the compiler, there's really no limit in the number of failing tests that can be...

----- Original Message ----- > ----- Original Message ----- > > Great job, Hal! > > > > Sure. I'd be happy to run icFuzz and report the fails once these > > bugs > > are fixed and thereafter whenever people want new runs. Obviously, > > this can be automated, but the problem is that icFuzz is not > > currently open sourced. > > I would be happy to see this open sourced, but I think that...

...(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; &...

...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 <...

The tests by design are syntactically correct, semantically correct, and have deterministic output. -moh From: Nick Lewycky [mailto:nlewycky at google.com] Sent: Monday, June 24, 2013 4:14 PM To: Haghighat, Mohammad R Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk On 24 June 2013 16:10, Haghighat, Mohammad R <mohammad.r.haghighat at intel.com<mailto:mohammad.r.haghighat at intel.com>> wrote: Hi, I just submitted a bug report with a package containing 107 small tes...

...est 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...

...est 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 pu...

...est 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...

...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 te...

...in 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...

On Mon, Jun 24, 2013 at 11:20:09PM +0000, Haghighat, Mohammad R wrote: > The tests by design are syntactically correct, semantically correct, and have deterministic output. > > -moh Hi, I wanted to believe you had a randomized code generator that could cover the entire valid input space. (smiles ;) But the test cited was not generated by a randomized code generator. It is way too

Hi Karen, Thanks much for your comment and for sharing of your experience. icFuzz has a core that is "really" random, but does not cover the entire C space. The tool was designed from scratch to be extensible, and comes with a couple of extensions that target some of compiler optimizations optimizing compilers typically do: CSE, loop interchange, vectorization, etc. Bu...

I meant "yes", the tests are non-floating-point.