Re:Tail Call Improvements in .NET Framework 4
by Gobiner on Tuesday March 09, 2010 @05:34PM
(#1179574)
If you think a feature that could potentially behave differently in RELEASE and DEBUG modes is problematic, you'll want to avoid floats and doubles in .NET. Runtime optimizations that do calculations in the processor's 80-bit FPU can alter the results of float/double calculations. My personal example: http://stackoverflow.com/questions/2225503/clr-jit-optimizat...
[ Parent
| on HN ]
Re:Tail Call Improvements in .NET Framework 4
by pcarmichael on Tuesday March 09, 2010 @08:41PM
(#1179948)
If you want identical results regardless of optimization level or machine characteristics, you should really be using fixed-point instead.