Boost C++ Libraries: Ticket #9533: boost::accumulators::weighted_median different results for debug and release modes https://svn.boost.org/trac10/ticket/9533 <p> I have a different results for debug and release modes. Look at readme and example in </p> <p> <a class="ext-link" href="https://github.com/aurusov/boost_accumulators_weighted_median_error"><span class="icon">​</span>https://github.com/aurusov/boost_accumulators_weighted_median_error</a> </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9533 Trac 1.4.3 Eric Niebler Mon, 30 Dec 2013 07:38:13 GMT owner changed https://svn.boost.org/trac10/ticket/9533#comment:1 https://svn.boost.org/trac10/ticket/9533#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Eric Niebler</span> to <span class="trac-author">Matthias Troyer</span> </li> </ul> <p> Matthias, can you comment? I know that the P<sup>2</sup> algorithm requires *far* more samples than is being provided here for any reasonable accuracy, but I can't fathom why the result should be different for different optimization levels. I don't believe gcc does unsafe floating point optimizations unless you specifically tell it to. Or am I mistaken about that? </p> Ticket