search for: xalanc

...all into a constant NaN, given the right options (-O2 -ffast-math for gcc, -O2 -qignerrno for xlc). All of gcc, icc, and xlc produce NaN via the library call with unoptimized code. Choosing 0.0 for Clang/LLVM introduces an unnecessary incompatibility. This is important in practice because of the xalanc benchmark in SPEC CPU2006. This code initializes a variable to a NaN value by assigning it the value sqrt(-2.01) -- don't ask me why. This variable is used to terminate a loop, and when Clang/LLVM produces 0.0 instead of NaN, the loop spins forever. Are there any objections to changing the L...

The large percentages are from those tiny benchmarks. If you look at omnetpp (0.52%), and xalanc (1.46%), the increase is small. To get a better average increase, you can sum up total debug_line size before and after and compute percentage accordingly. David On Thu, Oct 27, 2016 at 1:11 PM, Dehao Chen <dehao at google.com> wrote: > The impact to debug_line is actually not small. I...

> On Sep 25, 2014, at 6:41 PM, Tim Northover <t.p.northover at gmail.com> wrote: > >> This is important in practice because of the xalanc benchmark in SPEC >> CPU2006. > > No, it would be important in practice for really used legacy (i.e. > unfixable) code relying on this undefined behaviour. It's important > for gaming the system if it occurs in SPEC. We should fix it because it costs us nothing to do and con...

...ilc 23.59% 444.namd 6.25% 447.dealII 8.43% 450.soplex 2.41% 453.povray 5.40% 470.lbm 0.00% 482.sphinx3 7.10% 400.perlbench 2.77% 401.bzip2 9.62% 403.gcc 2.67% 429.mcf 9.54% 445.gobmk 7.40% 456.hmmer 9.79% 458.sjeng 9.98% 462.libquantum 10.90% 464.h264ref 30.21% 471.omnetpp 0.52% 473.astar 5.67% 483.xalancbmk 1.46% mean 7.86% Dehao On Thu, Oct 27, 2016 at 11:55 AM, Xinliang David Li <davidxl at google.com> wrote: > Do you have an estimate of the debug_line size increase? I guess it will > be small. > > David > > On Thu, Oct 27, 2016 at 11:39 AM, Dehao Chen <dehao at googl...

...his is not true for the ARM ELLCC due to the ecc binary becoming too large). ## On the mailing lists * Bill Schmidt started off an interesting discussion about [whether sqrt of a negative number should be optimised to 0 or NaN](http://article.gmane.org/gmane.comp.compilers.llvm.devel/77238). The xalanc benchmark in SPEC CPU2006 relies on it returning a NaN apparently. * Chandler Carruth has posted an RFC proposing that [LLVM should require a working C++11 thread, mutex, and atomic](http://article.gmane.org/gmane.comp.compilers.llvm.devel/77148) with the intention being that support for MinGW and...