"H.J. Lu" <hjl.to...@gmail.com> writes: > Sometime I have to do > > int x = 0; > > to silence gcc from uninitialized warnings when I know it is > unnecessary. Is that a good idea to add > > int x __attribute__ ((uninitialized)); > > to tell compiler that it is OK for "x" to be uninitialized?
I think the general idea is reasonable. I also think it might be worth spending a few minutes thinking about whether we can implement some more general diagnostic suppression mechanism. E.g., int x __attribute__ ((ignore ("-Wuninitialized"))); Ian