“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 rini17 on Monday July 15, 2019 @06:05AM (#20439381)

Then later, after some minor unrelated change, compiler stops optimizing and it suddenly starts overflowing the stack.

How can anyone put up with that?

[ Parent | on HN ]

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

If you rely on an optimization like this, that's not a code smell as much as a code-sewer:

This is one of those optimizations that a very clever compiler might be able to do interprocedurally give a certain input for example.

[ Parent | on HN ]

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

I expect the compiler would optimize the tail recursion into a loop, so the likely worst case is not that you blow the stack but that you spin for a while.

[ Parent | on HN ]

Re:“What the Hardware Does” Is Not What Your Program Does: U... by rini17 on Tuesday July 16, 2019 @06:18AM (#20448806)

Not really, any expectations here are unsupported by C standards. Compiler is, by spec, allowed to do anything here.

[ Parent | on HN ]