... and the answer is that it's 32-bit-specific, or at least I can reproduce the data corruption on i686 F-13 and not x86_64. I don't see the other warnings that were mentioned in the upstream thread, though.
Getting rid of -ffast-math does appear to fix it. I'll spin new RPMs with that fix shortly. Please test.
... and the answer is that it's 32-bit-specific, or at least I can reproduce the data corruption on i686 F-13 and not x86_64. I don't see the other warnings that were mentioned in the upstream thread, though.
Getting rid of -ffast-math does appear to fix it. I'll spin new RPMs with that fix shortly. Please test.