Re:The Problem with Friendly C
by pcwalton on Wednesday December 23, 2015 @11:04PM
(#10787064)
> Apparently a (uint32_t) shifted by 32 is license to become completely insane.
That's easy to explain. The optimizer replaced the instruction with an undef [1], which has no live range. So it printed the value of some random register, which happened to be 0, 0x5a788cb0, or 0x54049be8.
That's easy to explain. The optimizer replaced the instruction with an undef [1], which has no live range. So it printed the value of some random register, which happened to be 0, 0x5a788cb0, or 0x54049be8.
[1]: http://llvm.org/docs/LangRef.html#undefined-values