Oh I have another question: Does this actually turn accessing the uninitialized variables into defined behavior, or can the optimizer still treat it as undefined behavior and thus do whatever it want?
Given that this *is* undefined behavior, turning it into defined behavior with a 0 value would be incredibly useful. It likely also breaks some code written to exploit legacy gcc behaviour, but oh well, that is broken anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972043 Title: Please add -ftrivial-auto-var-init=zero to default build flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1972043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
