Re:“What the Hardware Does” Is Not What Your Program Does: U...
by quotemstr on Sunday July 14, 2019 @05:22PM
(#20436139)
I disagree that bit and byte level uninitialized models are equivalent. Consider a program that uses one bit of a bitfield in a stack allocated strict. The compiler is free to preserve the value of that bit however it pleases --- e.g., in the carry flag --- and randomize the rest of the bits if you ever read the whole byte.
[ Parent
| on HN ]
Re:“What the Hardware Does” Is Not What Your Program Does: U...
by ralfjung on Monday July 15, 2019 @08:03AM
(#20439984)
Hm, good point about the bitfields. The paper I cite [1] actually talks specifically about bitfields as their precise semantics in the presence of "poison"-style uninitialized memory is not entirely clear yet.