> same uninitialized value, that can limit code generation options it pretty much requires the compiler to initialize all values when they first "appear" exce

> same uninitialized value, that can limit code generation options it pretty much requires the compiler to initialize all values when they first "appear" except that this is impossible and outright hazardous if pointers are involved But doable for a small subset like e.g. - stack values (but would inhibit optimizations, potentially pretty badly) - some allocations e.g. I/O buffers, (except C alloc has no idea that you are allocating an I/O buffer)