search for: _proven_

...sum.sext can now be something other than all zeroes or all ones. > Actually optimizing code that we've proven has undefined behavior, in contrast, is basically uninteresting and leads us into these silly philosophical problems. I don't think we care about optimizing code that we've _proven_ has undefined behavior. We care about optimizing code in ways that is correct in the face of *other* transforms that we ourselves want to do, where these "other transforms" pretend certain abnormal cases do not exist. Poison is a "stand-in" for these transforms, which are some...

..., because the counter-factual still applies. > >>> Actually optimizing code that we've proven has undefined behavior, in contrast, is basically uninteresting and leads us into these silly philosophical problems. >> I don't think we care about optimizing code that we've _proven_ has >> undefined behavior. We care about optimizing code in ways that is >> correct in the face of *other* transforms that we ourselves want to >> do, where these "other transforms" pretend certain abnormal cases do >> not exist. Poison is a "stand-in"...

> On 11/8/2016 3:32 PM, Sanjoy Das wrote: >> Hi Nuno, Chandler, >> >> Nuno Lopes via llvm-dev wrote: >> > This program stores 8 bits, and leaves the remaining 24 bits >> > uninitialized. It then loads 16 bits, half initialized to %v, half >> > uninitialized. SROA transforms the above function to: >> > >> > define i16 @g(i8 %in) {