-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/06/11 12:21, Ian Lance Taylor wrote: > While using the optimizers to improve the quality of uninitialized > warnings does have some benefits, those benefits are outweighed by > the drawbacks. We need to completely reimplement this warning, > either in the C/C++ common frontend, or before any optimization > passes run. Run it just after going into SSA; mark everything that has an uninitialized use. For those who want the larger, much more stable set of warnings this is going to meet their needs much better.
That's what my patch from a few years ago did. IIRC the only outstanding issue was what should the default be. In theory we could go ahead and translate into SSA when not optimizing which would remove the dependency on -O, at the expense of compile-time performance. > > Then we can rename the existing warning to > -Wunpredictable-uninitialized and take it out of -Wall. I'd tend to think this would be a mistake. We'd be changing -Wall in a very very visible way and I suspect the number of developers complaining would be huge. Ideally we'd just nuke -Wall and have everyone use the -W options they care about, but sadly that's just a pipe dream. jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO3m4mAAoJEBRtltQi2kC7kw8H/1cxi3gj76qEBsnaCvyxEdKA REZ7t8tQpk5sjyNB9SmmSMQWeTJaMWWXFk5WlpCmoplxbf98/8hqz/lpUP0+WKBC 2GrkQQ4cCYpVtthjs2XZpaHAzNbDaUutjlmDJn98MzeisF7x5mWT00gxy7IufgNR fGe79a3ojLF6tMpMsgoRMKcP/uX8TKP2KBzwj1LSpNv9H8dd1xqM7POiVNnWwZ2X 2s6uozkVBJuInh6SgjikZTqOyXCtnBVHwC1zJa3WKUPI9bYJL3LZr8+KCXe4WFj3 s4hVukgcjYjtChioiDVJhD4tJ8jaUyMx6cKQXJC6VlLXT39Uzh+oM1UQdyfVQsM= =jS8p -----END PGP SIGNATURE-----
