search for: 107364

Displaying 5 results from an estimated 5 matches for "107364".

Did you mean: 007364
2010 Aug 23
1
Strange space characters in character strings
...uot;117381 " "100000 " " " " 275417" "266459" " 214552" [53] "207312" "173557" "167647" "150516" "135842" "126667" "131642" "113804" "107364" "108242" " 102881" " 100000" Looks fine to me. Now I can use as.numeric() to convert to numbers (leading and lagging spaces should not be a problem): > as.numeric(gsub("[$,]", "", as.character(moose$V3))) [1] NA NA NA...
2017 Jan 24
3
[InstCombine] rL292492 affected LoopVectorizer and caused 17.30%/11.37% perf regressions on Cortex-A53/Cortex-A15 LNT machines
...so I wonder if we can pin any other perf changes from this commit. > > I'm new to using the LNT site, but this should be the full set of results for the A53 machine in question with a baseline (r292491) before this patch and current (r292522) : > http://llvm.org/perf/db_default/v4/nts/107364 <http://llvm.org/perf/db_default/v4/nts/107364> > > If these are reliable results, we have 2 perf wins (puzzle, gramschmidt) on the A53 machine. How do we determine the importance of the sieve benchmark vs. the rest of the suite? > > An x86 machine doesn't show any regressio...
2017 Jan 24
2
[InstCombine] rL292492 affected LoopVectorizer and caused 17.30%/11.37% perf regressions on Cortex-A53/Cortex-A15 LNT machines
> On Jan 23, 2017, at 3:48 PM, Sanjay Patel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > All targets are likely affected in some way by the icmp+shl fold introduced with r292492. It's a basic pattern that occurs in lots of code. Did you see any perf wins on your targets with this commit? > > Sadly, it is also likely that many (all?) targets are negatively
2017 Jan 24
3
[InstCombine] rL292492 affected LoopVectorizer and caused 17.30%/11.37% perf regressions on Cortex-A53/Cortex-A15 LNT machines
...improve perf, so I wonder if we can pin any other perf changes from this commit. I'm new to using the LNT site, but this should be the full set of results for the A53 machine in question with a baseline (r292491) before this patch and current (r292522) : http://llvm.org/perf/db_default/v4/nts/107364 If these are reliable results, we have 2 perf wins (puzzle, gramschmidt) on the A53 machine. How do we determine the importance of the sieve benchmark vs. the rest of the suite? An x86 machine doesn't show any regressions from this change: http://llvm.org/perf/db_default/v4/nts/107353 Are the...
2010 Aug 24
0
mlm for within subject design
...uot;117381 " "100000 " " " " 275417" "266459" " 214552" [53] "207312" "173557" "167647" "150516" "135842" "126667" "131642" "113804" "107364" "108242" " 102881" " 100000" Looks fine to me. Now I can use as.numeric() to convert to numbers (leading and lagging spaces should not be a problem): > as.numeric(gsub("[$,]", "", as.character(moose$V3))) [1] NA NA NA...