“What the Hardware Does” Is Not What Your Program Does: Uninitialized Memory

Re:“What the Hardware Does” Is Not What Your Program Does: U... by mehrdadn on Sunday July 14, 2019 @06:56PM (#20436796)

Depends how you look at it. They don't ignore it during translation but that's because they work hard to make the program "ignore it completely" (i.e., not spend a single cycle on the possibility) during execution.

[ Parent | on HN ]

Re:“What the Hardware Does” Is Not What Your Program Does: U... by mpweiher on Monday July 15, 2019 @06:04AM (#20439378)

(a) That's not what the text says.

(b) What compilers are doing does not match "ignore at execution", because they also use it to remove completely separate code.

[ Parent | on HN ]

Re:“What the Hardware Does” Is Not What Your Program Does: U... by mehrdadn on Monday July 15, 2019 @06:16AM (#20439414)

If stripping code whose only relevance is in a UB situation doesn't amount to ignoring the UB situation completely, I don't know what does. It's literally the production of code that is completely ignorant of the UB situation.

[ Parent | on HN ]

Re:“What the Hardware Does” Is Not What Your Program Does: U... by mpweiher on Monday July 15, 2019 @01:43PM (#20443258)

If that were what it does, I'd agree.

It isn't.

[ Parent | on HN ]

Re:“What the Hardware Does” Is Not What Your Program Does: U... by mehrdadn on Monday July 15, 2019 @01:46PM (#20443287)

If you could give an example to actually illustrate what you mean, maybe I'd agree too, but it's a little tough when you don't...

[ Parent | on HN ]