Paul Ishenin, a FPC developer, was the one who suggested this fix. I got the same impression, to what he replied clearly that this was a fix, not a workaround. It's something like this is to avoid trapping some FPU exceptions, since C code handles them differently, or that the CPU exception flag is leftover from the C library function call which C code wouldn't bother but FPC needs it to be explicitly cleared upon the function return...
-- Winff startup warning about access violation and possible data corruption https://bugs.launchpad.net/bugs/521818 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
