<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - floating-point-exceptions in gallium/auxiliary/tgsi/ functions" href="https://bugs.freedesktop.org/show_bug.cgi?id=108856#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - floating-point-exceptions in gallium/auxiliary/tgsi/ functions" href="https://bugs.freedesktop.org/show_bug.cgi?id=108856">bug 108856</a> from <a class="email" href="mailto:popinet@basilisk.fr" title="popinet@basilisk.fr">popinet@basilisk.fr</a> <pre>Thanks for your feedback. I understand we may have a different point-of-view due to different fields of application. > But even there, we don't mess with enabling/disabling exceptions, as it's simply > not our responsibility, we're just fine with the default of all exceptions > masked. I am sure you are fine with it, as are many other libraries. What I am saying is that turning them on may well help you find bugs that you could easily miss otherwise. At least this has been my experience over the years. It is a bit like using assert() and turning assertions on. If you are worried about performance, you can of course revert to the default in production.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>