search for: irsmk

Hi, Shrink-wrapping capabilities, i.e., better placement of prologue and epilogue sequences, landed in r236507 but are not yet enabled by default. Since r236507 AArch64 is shrink-wrapping ready, meaning we can turn the pass on for this target. I’ve done the same for X86 in r 238293. Now, I need your help to test and benchmark how shrink-wrapping perform on those targets. The goal is to decide

...t; > Tests Summary > > Status Group # > Performance Regressions 88 > Performance Improvements 1 > Unchanged Tests 872 > *Total Tests* *961* > > > Changes Detail > > Performance Regressions Δ Previous Current σ > MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk.compile 12.51% 0.7325 0.8241 0.0102 > SingleSource/UnitTests/ObjC++/property-reference.compile 7.39% 0.9252 0.9936 0.0064 > SingleSource/UnitTests/ObjC++/Hello.compile 7.33% 0.7822 0.8395 0.0015 > MultiSource/Benchmarks/VersaBench/dbms/dbms.compile 7.21% 1.1218 1.2027 0.0173 > Mul...

...us Group # >> Performance Regressions 88 >> Performance Improvements 1 >> Unchanged Tests 872 >> *Total Tests* *961* >> >> >> Changes Detail >> >> Performance Regressions Δ Previous Current σ >> MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk.compile 12.51% 0.7325 0.8241 0.0102 >> SingleSource/UnitTests/ObjC++/property-reference.compile 7.39% 0.9252 0.9936 0.0064 >> SingleSource/UnitTests/ObjC++/Hello.compile 7.33% 0.7822 0.8395 0.0015 >> MultiSource/Benchmarks/VersaBench/dbms/dbms.compile 7.21% 1.1218 1.2027 0.0...

Hi all, I've started looking at the GlobalMerge pass, enabled by default on ARM and AArch64. I think we should reconsider that, at least for AArch64. As is, the pass just merges all globals together, in groups of 4KB (AArch64, 128B on ARM). At the time it was enabled, the general thinking was "it's almost free, it doesn't affect performance much, we might as well use it".

tl;dr in low data situations we don’t look at past information, and that increases the false positive regression rate. We should look at the possibly incorrect recent past runs to fix that. Motivation: LNT’s current regression detection system has false positive rate that is too high to make it useful. With test suites as large as the llvm “test-suite” a single report will show hundreds of

...4.01% cumulative (2.41% - 138.98s this program) nts.SingleSource/Benchmarks/CoyoteBench/almabench.exec > 5. 26.32% cumulative (2.32% - 133.59s this program) nts.MultiSource/Applications/lua/lua.exec > 6. 28.26% cumulative (1.94% - 111.80s this program) nts.MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk.exec > 7. 30.11% cumulative (1.85% - 106.56s this program) nts.MultiSource/Benchmarks/ASC_Sequoia/AMGmk/AMGmk.exec > 8. 31.60% cumulative (1.49% - 86.00s this program) nts.SingleSource/Benchmarks/CoyoteBench/huffbench.exec > 9. 32.75% cumulative (1.15% - 66.37s this program) nts.M...

.../Benchmarks/MallocBench/cfrac/cfrac | * | * | MultiSource/Benchmarks/PAQ8p/paq8p | * | * | MultiSource/Benchmarks/ASC_Sequoia/AMGmk/AMGmk | * | * | MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk | * | * | MultiSource/Benchmarks/ASC_Sequoia/CrystalMk/CrystalMk | * | * | MultiSource/Benchmarks/Fhourstones/fhourstones | * | * | MultiSource/Benchmarks/Trimaran/netbench-crc/netbench-crc...

...0.00368025909023 Benchmarks/TSVC/StatementReordering-dbl/Sta 2.5547 2.555 0.01174306180765 Benchmarks/Trimaran/enc-md5/enc-md5 1.2119 1.2126 0.05776054129878 Benchmarks/MiBench/automotive-basicmath/aut 0.1698 0.1699 0.05889281507655 Benchmarks/ASC_Sequoia/IRSmk/IRSmk 2.6607 2.6626 0.07140977938136 Benchmarks/Fhourstones-3.1/fhourstones3.1 0.7427 0.7433 0.08078632018310 Benchmarks/TSVC/LoopRestructuring-dbl/LoopR 2.9857 2.9883 0.08708175637204 Benchmarks/Olden/em3d/em3d 2.0241 2.0262 0...

Andy and I briefly discussed this the other day, we have not yet got chance to list a detailed pass order for the pre- and post- IPO scalar optimizations. This is wish-list in our mind: pre-IPO: based on the ordering he propose, get rid of the inlining (or just inline tiny func), get rid of all loop xforms... post-IPO: get rid of inlining, or maybe we still need it, only

....579802023| 4.7|38512062691| -1.3|4.577213823| 4.76|38512062692| -1.3| |MultiSource/Benchmarks/ASC_Sequoia/CrystalMk/CrystalMk.test | 40|2.942015001|26934039129|2.943005397| -0.03|26934039124| 0|2.942780883| -0.03|26934039124| 0| |MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk.test | 40|2.212075899| 8974161060|2.208563573| 0.16| 8974289110| 0| 2.20958891| 0.11| 8974289109| 0| |MultiSource/Benchmarks/BitBench/drop3/drop3.test | 169|0.165502473| 1989074268|0.165868692| -0.22| 1989074282| 0|0.16...

...8 | 0.98    0.99    n/a          n/a > MultiSource/Benchmarks/ASC_Sequoia/CrystalMk/CrystalMk                   | > 0.0500 8296     0.0500      *                0.0300      |    8.83    8.73 >  8.69 *           8.77 | 1.01    1.02    n/a          n/a > MultiSource/Benchmarks/ASC_Sequoia/IRSmk/IRSmk                           | > 0.0100 5600     0.0300      *                0.0300      |    0.00    0.00 >  0.00 *           0.04 | -       -       n/a          n/a > MultiSource/Benchmarks/BitBench/drop3/drop3                              | > 0.0200 3592     0.0199      *        ...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

....99 n/a n/a > MultiSource/Benchmarks/ASC_Sequoia/CrystalMk/ > CrystalMk | 0.0500 8296 0.0500 > * 0.0300 | 8.83 8.73 8.69 * > 8.77 | 1.01 1.02 n/a n/a > MultiSource/Benchmarks/ASC_Sequoia/IRSmk/ > IRSmk | 0.0100 5600 0.0300 > * 0.0300 | 0.00 0.00 0.00 * > 0.04 | - - n/a n/a > MultiSource/Benchmarks/BitBench/drop3/ > drop3 | 0.0200 3592 0.0199...

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make