search for: r325313

...gt;The builder is reliable. Please pay attention on the failures. > >The performance statistics are here: >http://lnt.llvm.org/db_default/v4/link/recent_activity > >Thanks > >Galina Great news, thanks ! Looking on results I am not sure how to explain them though. For example r325313 fixes "use after free", it should not give any performance slowdowns or boosts. Though if I read results right, they show 23.65% slowdown for time of linking linux kernel (http://lnt.llvm.org/db_default/v4/link/104). I guess such variation can happen for example if bot do only single lin...

...after the commit, so, I do not think this one is an outliner. For example, if one would take a look at the linux-kernel branches - http://lnt.llvm.org/db_default/v4/link/graph?plot.0=1.12.2&highlight_run=104, it gets obvious that the number of branches increased significantly as a result of the r325313. The metric is very stable around the impacted commit and does not go down after. The branch-misses is more volatile, but still consistently shows the regression as the result of this commit. Now someone should see why this particular commit has resulted in significant increase of branching with...

...o not think > this one is an outliner. > For example, if one would take a look at the linux-kernel branches - > http://lnt.llvm.org/db_default/v4/link/graph?plot.0=1.12.2&highlight_run=104, > it gets obvious that the number of branches increased significantly as a > result of the r325313. The metric is very stable around the impacted commit > and does not go down after. The branch-misses is more volatile, but still > consistently shows the regression as the result of this commit. > > Now someone should see why this particular commit has resulted in > significant inc...

...is an outliner. > > For example, if one would take a look at the linux-kernel branches - > > http://lnt.llvm.org/db_default/v4/link/graph?plot.0= > 1.12.2&highlight_run=104, > > it gets obvious that the number of branches increased significantly as a > > result of the r325313. The metric is very stable around the impacted > commit > > and does not go down after. The branch-misses is more volatile, but > still > > consistently shows the regression as the result of this commit. > > > > Now someone should see why this particular commit has re...