[PATCH] D47963: [LangRef] Clarify that nnan and ninf don't produce undef or poison.

[Hal Finkel via Phabricator via llvm-commits]

hfinkel added a comment.

I don't think this is right. Saying the result is undefined seems like what we intend. We might choose, as an implementation technique, to limit how we take advantage of that undefinedness in certain cases, but the violating the constraint still produces logical inconsistencies that can transfer to other parts of the code, and in general, turn into any other kind of undefined behavior (depending on the structure of the code).


Repository:
  rL LLVM

https://reviews.llvm.org/D47963