search for: matrix01

Displaying 6 results from an estimated 6 matches for "matrix01".

Did you mean: matrix
2015 Nov 19
2
Recent -Os code size regressions
Hello LLVM, Does the community have bots or humans tracking code size for -Os builds? I've noticed troubling regressions lately. Sometime near Nov 5, the EEMBC bitmnp01 benchmark grew by 25% for ARMv7m and 35% for i586. That's ghastly. This week, the EEMBC matrix01 workload grew by 5% for ARMv7m and 3% for i586. Regards, -steve
2015 Nov 21
2
Recent -Os code size regressions
...or SPEC on ARM. I do > track performance every release, but not code size at -Os. > >> I've noticed troubling regressions lately. Sometime near Nov >> 5, the EEMBC bitmnp01 benchmark grew by 25% for ARMv7m and 35% for >> i586. That's ghastly. This week, the EEMBC matrix01 workload grew by >> 5% for ARMv7m and 3% for i586. > > Hum, v7M is even lower priority for me at the moment. :) > > Though, I have to say, 25% is really bad. Can you bisect to see which > commit was that? Hi Renato, Thanks for advising. The commit is: [llvm] r252152 - [Simpl...
2015 Nov 21
3
Recent -Os code size regressions
...or SPEC on ARM. I do > track performance every release, but not code size at -Os. > >> I've noticed troubling regressions lately. Sometime near Nov >> 5, the EEMBC bitmnp01 benchmark grew by 25% for ARMv7m and 35% for >> i586. That's ghastly. This week, the EEMBC matrix01 workload grew by >> 5% for ARMv7m and 3% for i586. > > Hum, v7M is even lower priority for me at the moment. :) > > Though, I have to say, 25% is really bad. Can you bisect to see which > commit was that? Hi Renato, Thanks for advising. The commit is: [llvm] r252152 - [Simpl...
2013 Jan 29
0
[LLVMdev] [Patch][Review Requested][Compilation Time] Avoid frequent copy of elements in LoopStrengthReduce
On Tue, Jan 29, 2013 at 3:59 PM, Murali, Sriram <sriram.murali at intel.com> wrote: > Our benchmark results show that the compilation time performance improved by > ~0.5%. That's fairly small; what was the standard deviation, confidence interval, etc? -- Sean Silva
2013 Jan 30
1
[LLVMdev] [Patch][Review Requested][Compilation Time] Avoid frequent copy of elements in LoopStrengthReduce
...jeng 100.00 100.70 464.h264ref 100.00 102.10 470.lbm 100.00 100.07 471.omnetpp 100.00 100.36 bitmnp01 100.00 100.44 cjpegv2data6 100.00 100.76 idctrn01 100.00 99.83 libquake2 100.00 100.08 libquake_portable 100.00 100.02 libxcsoar 100.00 100.08 linpack 100.00 101.07 matrix01 100.00 100.28 nbench 100.00 100.76 tblook01 100.00 101.52 ttsprk01 100.00 100.82 Geomean 100.00 100.51 -----Original Message----- From: Sean Silva [mailto:silvas at purdue.edu] Sent: Tuesday, January 29, 2013 6:41 PM To: Murali, Sriram Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLV...
2013 Jan 29
4
[LLVMdev] [Patch][Review Requested][Compilation Time] Avoid frequent copy of elements in LoopStrengthReduce
Hello, This patch aims to improve compile time performance by increasing the SCEV vector size in LoopStrengthReduce. It is observed that the BaseRegs vector size is 4 in most cases, and elements are frequently copied when it is initialized as SmallVector<const SCEV *, 2> BaseRegs. Our benchmark results show that the compilation time performance improved by ~0.5%. Patch by Wan Xiaofei.