Displaying 2 results from an estimated 2 matches for "ensureisnonpoison".
2016 Oct 21
4
RFC: Killing undef and spreading poison
...t all) LLVM analyses today report a result that doesn't exclude that the value might be poison. That's because if you report %v to be non-null and it's actually poison it's fine since poison can be restricted to be non-null. We will need to introduce a isNotPoison() analysis and a ensureIsNonPoison() utility (that needs to be used by all transformations doing speculation).
I would freeze %y. What's the argument against?
> Auto-vectorization, converting adjacent scalar memory accesses into vector accesses, or into wider combined scalar accesses is a concern. If widening a load causes...
2016 Oct 18
8
RFC: Killing undef and spreading poison
Hi,
Over the past few years we've been trying to kill poison somehow. There have
been a few proposals, but they've all failed to pass the bar and/or to
gather significant support (my own proposals included).
We (David, Gil, John, Juneyoung, Sanjoy, Youngju, Yoonseung, and myself)
have a new proposal to kill undef instead and replace it with poison + a new
'freeze' instruction. We