Displaying 3 results from an estimated 3 matches for "3a663359".
2013 Dec 11
2
[LLVMdev] Float undef value propagation
Well in IEEE-754 Nan + any value returns Nan, so doing Nan + undef -> undef is wrong.
I agree that undef are usually the results of a bad application behavior I'm just wondering what is the right thing to do.
Thomas
-----Original Message-----
From: Tim Northover [mailto:t.p.northover at gmail.com]
Sent: Wednesday, December 11, 2013 12:15 PM
To: Raoux, Thomas F
Cc: Philip Reames; llvmdev
2013 Dec 11
0
[LLVMdev] Float undef value propagation
On 11 December 2013 20:25, Raoux, Thomas F <thomas.f.raoux at intel.com> wrote:
> Well in IEEE-754 Nan + any value returns Nan, so doing Nan + undef -> undef is wrong.
I see what you mean having re-read the language reference. It looks
like LLVM's "undef" has to be *some* bitpattern at any point, and that
allows IEEE room to come in and say what the result is.
Tim.
2013 Dec 11
2
[LLVMdev] Float undef value propagation
...re true for all values of a type must also be true for undef. Because NaN + x == NaN is true for all values of x, it must also be true for undef.
—Owen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131211/3a663359/attachment.html>