search for: fatigue0

...and attach the BC files for the >> major loops >> that we miss ? > > I took a look and it's not clear what vectorization has to do with it, > it seems > to be a missed fast-math optimization. I've attached bitcode where > only LLVM > optimizations are run (fatigue0.ll) and where GCC optimizations are > run before > LLVM optimizations (fatigue1.ll). The hottest instruction is the same > in both: > > fatigue0.ll: > %329 = fsub fast double %327, %328, !dbg !1077 > > fatique1.ll: > %1504 = fsub fast double %1501, %1503, !dbg !114...

Hi Jack, thanks for splitting out what the effects of LLVM's / GCC's vectorizers is. On 01/06/13 21:34, Jack Howarth wrote: > On Sat, Jun 01, 2013 at 06:45:48AM +0200, Duncan Sands wrote: >> >> These results are very disappointing, I was hoping to see a big improvement >> somewhere instead of no real improvement anywhere (except for gas_dyn) or a >> regression

Jack, Can you please file a bug report and attach the BC files for the major loops that we miss ? Thanks, Nadav On Jun 2, 2013, at 1:27, Duncan Sands <duncan.sands at gmail.com> wrote: > Hi Jack, thanks for splitting out what the effects of LLVM's / GCC's vectorizers > is. > > On 01/06/13 21:34, Jack Howarth wrote: >> On Sat, Jun 01, 2013 at 06:45:48AM +0200,