[LLVMdev] RFC: Proposal for Poison Semantics

Bruce Hoult bruce at protection.opia.illinois.edu
Wed Jan 28 21:59:38 PST 2015


On Thu, Jan 29, 2015 at 6:24 PM, Philip Reames <listmail at philipreames.com>
wrote:

>  This is different from undef in that there may be bits in the output
> whose values would be known for *any* specific value chosen for the poison
> input.  For undef, these bits would not be undef and would instead be
> known.  For poison, these bits are unconditionally poison.
>
> (I'm having a hard time finding an example for this part; this implies it
> probably isn't true.)
>
>
undef xor undef == 0 but poison xor poison == poison ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150129/66b297ec/attachment.html>


More information about the llvm-dev mailing list