search for: pr16460

...of root problems are expected. > > Any help with triaging these bugs would be highly appreciated. I've gone through all of the miscompile cases, used bugpoint to reduce them, and opened individual PRs for several distinct bugs. So far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 (instcombine). Thanks again for doing this! Do you plan on repeating this testing on a regular basis? Can it be automated? -Hal > > Thanks, > -moh > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiu...

.... > > > > Any help with triaging these bugs would be highly appreciated. > > I've gone through all of the miscompile cases, used bugpoint to > reduce them, and opened individual PRs for several distinct bugs. So > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > (instcombine). Thanks again for doing this! Do you plan on repeating > this testing on a regular basis? Can it be automated? > > -Hal > > > > > Thanks, > > -moh > > > > _______________________________________________ > > LLVM Developers mail...

...of root problems are expected. > > Any help with triaging these bugs would be highly appreciated. I've gone through all of the miscompile cases, used bugpoint to reduce them, and opened individual PRs for several distinct bugs. So far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 (instcombine). Thanks again for doing this! Do you plan on repeating this testing on a regular basis? Can it be automated? -Hal > > Thanks, > -moh > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiu...

...p with triaging these bugs would be highly appreciated. > > > > I've gone through all of the miscompile cases, used bugpoint to > > reduce them, and opened individual PRs for several distinct bugs. > > So > > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > > (instcombine). Thanks again for doing this! Do you plan on > > repeating > > this testing on a regular basis? Can it be automated? > > > > -Hal > > > > > > > > Thanks, > > > -moh > > > > > > __________________...

...p with triaging these bugs would be highly appreciated. > > > > I've gone through all of the miscompile cases, used bugpoint to > > reduce them, and opened individual PRs for several distinct bugs. > > So > > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > > (instcombine). Thanks again for doing this! Do you plan on > > repeating > > this testing on a regular basis? Can it be automated? > > > > -Hal > > > > > > > > Thanks, > > > -moh > > > > > > __________________...

...s would be highly appreciated. > > > > > > I've gone through all of the miscompile cases, used bugpoint to > > > reduce them, and opened individual PRs for several distinct bugs. > > > So > > > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > > > (instcombine). Thanks again for doing this! Do you plan on > > > repeating > > > this testing on a regular basis? Can it be automated? > > > > > > -Hal > > > > > > > > > > > Thanks, > > > > -moh >...

...with triaging these bugs would be highly appreciated. > > > > I've gone through all of the miscompile cases, used bugpoint to > > reduce them, and opened individual PRs for several distinct bugs. > > So > > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > > (instcombine). Thanks again for doing this! Do you plan on repeating > > this testing on a regular basis? Can it be automated? > > > > -Hal > > > > > > > > Thanks, > > > -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

...> > > > > I've gone through all of the miscompile cases, used bugpoint to > > > > reduce them, and opened individual PRs for several distinct > > > > bugs. > > > > So > > > > far we have: PR16455 (loop vectorizer), PR16457 (sccp), PR16460 > > > > (instcombine). Thanks again for doing this! Do you plan on > > > > repeating > > > > this testing on a regular basis? Can it be automated? > > > > > > > > -Hal > > > > > > > > > > > > > &g...

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