https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119179
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Do you have a good example where this should be used? I am thinking using on uninitialized on a class is even more error-prone and invasive rather than on variables themselves. Even more this is a security feature so using uninitialized should be using sparsely in the first place. >are used as "buffers" on the stack are now automatically filled with byte >patterns. This is exactly when you don't want this.
