Diff Detail
Unit Tests
Time | Test | |
---|---|---|
60,050 ms | x64 debian > libFuzzer.libFuzzer::fuzzer-leak.test | |
60,040 ms | x64 debian > libFuzzer.libFuzzer::minimize_crash.test |
Event Timeline
Seems reasonable. Can we get alive2 proofs for floating point things like this yet @nlopes?
Alive2 says this is ok and seems to understand copysign. For some of the other complex functions in other patches, it doesn’t complain but it also doesn’t complain when I try things that are obviously wrong
Most FP stuff should be working now. Exceptions include: some fast-math flags (arcp/contract/reassoc/afn), exceptions, and some intrinsics. The rest should all be working; if not please file a bug report :)
As noted above, most FP should be working. If Alive2 misses a bug, please do file a bug report. Alive2 is not supposed to miss (almost no) bugs.
llvm/test/Transforms/InstSimplify/floating-point-arithmetic.ll | ||
---|---|---|
964 | Something went wrong - this is a miscompile without 'nsz' on the sqrt (otherwise, it can return -0.0): |
llvm/test/Transforms/InstSimplify/floating-point-arithmetic.ll | ||
---|---|---|
964 | But this is being consumed by an fcmp - the sign of the zero shouldn't matter for the final result. Alive bug? |
llvm/test/Transforms/InstSimplify/floating-point-arithmetic.ll | ||
---|---|---|
964 | No - the negative sign of the -0.0 is applied to the magnitude parameter (%unknown). |
Something went wrong - this is a miscompile without 'nsz' on the sqrt (otherwise, it can return -0.0):
https://alive2.llvm.org/ce/z/yqXQmQ