search for: haghighat

...submitted 27 failing tests on clang version 3.5, trunk 199158. http://llvm.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...

...their root causes could be the same as before or could actually be > new bugs. Great, thanks! I'll go through them. -Hal > > 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 attachme...

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

On 24 June 2013 16:10, Haghighat, Mohammad R <mohammad.r.haghighat at intel.com > wrote: > 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,...

...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 clang 3.4 trunk ----- Original Message ----- > ----- Original Message ----- > > Great job, Hal! > > > > Sure. I'd be happy to run icFuzz...

...libm implementation. Are there non-floating-point cases? > > Just let me know when you want a new run. Will do! -Hal > > Cheers, > -moh > > -----Original Message----- > From: Hal Finkel [mailto:hfinkel at anl.gov] > Sent: Wednesday, June 26, 2013 7:35 AM > To: Haghighat, Mohammad R > Cc: llvmdev at cs.uiuc.edu; Jim Grosbach > Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly > generated tests that fail on clang 3.4 trunk > > ----- Original Message ----- > > > > Hi Moh, > > > > > > Thanks for this....

.../show_bug.cgi?id=16431 These are new tests different from the previously posted ones, but their root causes could be the same 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 (ver...

...riginal Message ----- > > Hi Moh, > > > Thanks for this. I’m really glad to see the work you’re doing in this > area and believe it will be extremely helpful in improving the > quality of the compiler. > > > -Jim > > > > On Jun 24, 2013, at 4:10 PM, Haghighat, Mohammad R < > mohammad.r.haghighat at intel.com > wrote: > > > > > > 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, compila...

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

...bugs are fixed. We've also seen cases where the results of "clang -O2" are different on Mac vs. Linux/Windows. Just let me know when you want a new run. Cheers, -moh -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Wednesday, June 26, 2013 7:35 AM To: Haghighat, Mohammad R Cc: llvmdev at cs.uiuc.edu; Jim Grosbach Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk ----- Original Message ----- > > Hi Moh, > > > Thanks for this. I’m really glad to see the work you’re doing in th...

...thers also seem to have been resolved as well. Thanks again, Hal > > -Hal > > > > > Cheers, > > -moh > > > > -----Original Message----- > > From: Hal Finkel [mailto:hfinkel at anl.gov] > > Sent: Wednesday, June 26, 2013 7:35 AM > > To: Haghighat, Mohammad R > > Cc: llvmdev at cs.uiuc.edu; Jim Grosbach > > Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly > > generated tests that fail on clang 3.4 trunk > > > > ----- Original Message ----- > > > > > > Hi Moh, > > >...

Hi Moh, Thanks for this. I’m really glad to see the work you’re doing in this area and believe it will be extremely helpful in improving the quality of the compiler. -Jim On Jun 24, 2013, at 4:10 PM, Haghighat, Mohammad R <mohammad.r.haghighat at intel.com> wrote: > 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...

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

...cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Karen Shaeffer Sent: Monday, June 24, 2013 5:17 PM To: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help needed with analyzing randomly generated tests that fail on clang 3.4 trunk 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...

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

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

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

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