On Fri, Apr 25, 2025 at 08:40:23AM -0700, Kees Cook wrote: > This isn't the case: the feature was explicitly designed in both GCC > and Clang to not disrupt -Wuninitialized. But -Wuninitialized has been > so flakey for so long that it is almost useless (there was even > -Wmaybe-uninitialized added to try to cover some of the missed > diagnostics). I do remember a fair amount of bogus uninitialized variable warnings, but they could be easily shut up without negative impact on the code. Not getting any warnings at all on the other hand is catastrophic. > And it's one of the many reasons stack variable zeroing > is so important, since so much goes undiagnosed. :( That only helps if the expected but forgotten initialization value actually is zero.
