search for: leslie3d

...;metadata' and should not alias with any actual accesses in the program. I've compiled the same code with GCC and it was able to hoist most of the address calculations out as expected. GCC was able to hoist address calculations for Q also. This is an actual piece of code in SPECCPU2006 437.leslie3d and the loop I analyzed is in line 1630 of file tml.f. 437.leslie3d suffers horrible performance problems because of this and similar problems. Is there anyway to enable this optimization? Is there a way to flag in the IR that a particular locations is array dimension meta data? Thanks, Wonsun

...d not alias with any > actual accesses in the program. I've compiled the same code with GCC > and it was able to hoist most of the address calculations out as > expected. GCC was able to hoist address calculations for Q also. > > This is an actual piece of code in SPECCPU2006 437.leslie3d and the > loop I analyzed is in line 1630 of file tml.f. 437.leslie3d suffers > horrible performance problems because of this and similar problems. > > Is there anyway to enable this optimization? Is there a way to flag in > the IR that a particular locations is array dimension meta...

On Wednesday 30 July 2008 16:03, David Greene wrote: > Ok, I've been tracking down a remat bug for over a week. I think I finally > understand what is going on. This happens in specfp2006 leslie3d > compiled with our frontend and optimizer. Unfortunately, getting a > testcase is going to be impossible due to restrictions on SPEC > redistribution and the complexity of the sequence of events leading to the > bug. Hooray! I have a fix for this. I filed PR2634 as a placeholder an...

On Jul 22, 2010, at 4:18 PMPDT, Reza Yazdani wrote: > Hi, > > I ran Spec2006 with -O4. All integer benchmarks passed, but only 8 > out 17 of floating point benchmarks passed. Is this normal or I > made a mistake in my build? Hi Reza. Somebody on Linux should answer, but I don't think it's normal. You may have checked out the source at a moment when it had a bug

Hi, I ran Spec2006 with -O4. All integer benchmarks passed, but only 8 out 17 of floating point benchmarks passed. Is this normal or I made a mistake in my build? Reza -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100722/4c4a81a9/attachment.html>

...0.00135 RE 433.milc -- 16.5 -- S 434.zeusmp -- 0.00146 RE 435.gromacs -- 0.00138 RE 436.cactusADM -- 0.00135 RE 437.leslie3d -- 0.00141 RE 444.namd -- 19.4 -- S 447.dealII -- 19.7 -- S 450.soplex -- 0.0380 -- S 453.povray...

...netpp 15.6 15.6 0.00% 473.astar 13 13 0.00% 483.xalancbmk 21.9 21.9 0.00% GEOMEAN 19.0929865 19.00588287     0.46% 410.bwaves  15.2 15.2 0.00% 416.gamess CE CE #VALUE! 433.milc  19 18.6 2.15% 434.zeusmp    14.2 14.2 0.00% 435.gromacs       11.6 11.3 2.65% 436.cactusADM 8.31 7.89 5.32% 437.leslie3d 11 11 0.00% 444.namd   16 16 0.00% 447.dealII 25.4 25.4 0.00% 450.soplex 26.1 26.1 0.00% 453.povray 20.5 20.5 0.00% 454.calculix 8.44 8.3 1.69% 459.GemsFDTD  10.7 10.7 0.00% 465.tonto CE CE #VALUE! 470.lbm 38.1 31.5 20.95% 481.wrf 11.6 11.6 0.00% 482.sphinx3 28.2 26.9 4.83% GEOMEAN 15.91...

...> 483.xalancbmk 21.9 21.9 0.00% > GEOMEAN 19.0929865 19.00588287 0.46% > 410.bwaves 15.2 15.2 0.00% > 416.gamess CE CE #VALUE! > 433.milc 19 18.6 2.15% > 434.zeusmp 14.2 14.2 0.00% > 435.gromacs 11.6 11.3 2.65% > 436.cactusADM 8.31 7.89 5.32% > 437.leslie3d 11 11 0.00% > 444.namd 16 16 0.00% > 447.dealII 25.4 25.4 0.00% > 450.soplex 26.1 26.1 0.00% > 453.povray 20.5 20.5 0.00% > 454.calculix 8.44 8.3 1.69% > 459.GemsFDTD 10.7 10.7 0.00% > 465.tonto CE CE #VALUE! > 470.lbm 38.1 31.5 20.95% > 481.wrf...

Ok, I've been tracking down a remat bug for over a week. I think I finally understand what is going on. This happens in specfp2006 leslie3d compiled with our frontend and optimizer. Unfortunately, getting a testcase is going to be impossible due to restrictions on SPEC redistribution and the complexity of the sequence of events leading to the bug. The bug is extremely subtle and nasty. Therefore this explanation is very long and com...

...-- S > 434.zeusmp -- > 0.00146 RE > 435.gromacs -- > 0.00138 RE > 436.cactusADM -- > 0.00135 RE > 437.leslie3d -- > 0.00141 RE > 444.namd -- > 19.4 -- S > 447.dealII -- > 19.7 -- S > 450.soplex...

...13 0.00% > 483.xalancbmk 21.9 21.9 0.00% > GEOMEAN 19.0929865 19.00588287 0.46% > 410.bwaves 15.2 15.2 0.00% > 416.gamess CE CE #VALUE! > 433.milc 19 18.6 2.15% > 434.zeusmp 14.2 14.2 0.00% > 435.gromacs 11.6 11.3 2.65% > 436.cactusADM 8.31 7.89 5.32% > 437.leslie3d 11 11 0.00% > 444.namd 16 16 0.00% > 447.dealII 25.4 25.4 0.00% > 450.soplex 26.1 26.1 0.00% > 453.povray 20.5 20.5 0.00% > 454.calculix 8.44 8.3 1.69% > 459.GemsFDTD 10.7 10.7 0.00% > 465.tonto CE CE #VALUE! > 470.lbm 38.1 31.5 20.95% > 481.wrf 11.6 11.6 0.00% > 48...

...3% -7.88% 434.zeusmp 19.58 18.92 20.01 3.49% -2.16% 264976 273096 279569 -2.97% -5.22% 435.gromacs 13.67 12.96 13.54 5.49% 0.94% 1061640 1100340 1138544 -3.52% -6.75% 436.cactusADM 15.51 15.78 15.42 -1.77% 0.53% 847904 869614 910019 -2.50% -6.83% 437.leslie3d 15.90 14.65 15.35 8.60% 3.65% 102357 106347 111073 -3.75% -7.85% 444.namd 20.02 18.20 19.91 10.06% 0.55% 333622 332808 341476 0.24% -2.30% 447.dealII 33.17 27.53 31.54 20.49% 5.16% 3832100 3907425 4034575 -1.93% -5.02% 450.soplex 31.03 30....

...3% -7.88% 434.zeusmp 19.58 18.92 20.01 3.49% -2.16% 264976 273096 279569 -2.97% -5.22% 435.gromacs 13.67 12.96 13.54 5.49% 0.94% 1061640 1100340 1138544 -3.52% -6.75% 436.cactusADM 15.51 15.78 15.42 -1.77% 0.53% 847904 869614 910019 -2.50% -6.83% 437.leslie3d 15.90 14.65 15.35 8.60% 3.65% 102357 106347 111073 -3.75% -7.85% 444.namd 20.02 18.20 19.91 10.06% 0.55% 333622 332808 341476 0.24% -2.30% 447.dealII 33.17 27.53 31.54 20.49% 5.16% 3832100 3907425 4034575 -1.93% -5.02% 450.soplex 31.03 30....