search for: ormeasure

...hing because the person doing the fix didn’t fully understand the problem? Happens to me all the time. The correct software engineering decision here is to fix the definition of “undef”, delete “poison”, and not hoist “nsw” attributes. That is a no-brainer. There is nothing to try out, or test, ormeasure. That is simply the way it has to be to avoid the current set of problems. I cannot emphasize that last point enough, fixing the definition of “undef”, deleting “poison”, and not allowing “nsw” attributes to be hoisted, fixes all known problems, even including ones that weren’t thought of before...

...gt; doing the fix didn’t fully understand the problem? Happens to me all the time. > > The correct software engineering decision here is to fix the definition of “undef”, > delete “poison”, and not hoist “nsw” attributes. That is a no-brainer. There is nothing > to try out, or test, ormeasure. That is simply the way it has to be to avoid the current > set of problems. > > I cannot emphasize that last point enough, fixing the definition of “undef”, deleting > “poison”, and not allowing “nsw” attributes to be hoisted, fixes all known problems, > even including ones that w...

Part I. The original LangRef appeared to be “nice and pretty” and originally ‘undef’ did not seem to stick out. Then evidence came to light in the form of bug reports, and in the form of Dan Gohman’s email “the nsw story”, that all was not good for ‘undef’ [1,2]. A proposal was made based on that evidence. A presentation was made at an llvm gathering. A paper was written. The proposal has even