This tracker bug is going to be used to report all the packages that currently use -Werror during build, and thus are likely to fail when new GCC releases add more warnings. This also is the cause of many failures related to _FORTIFY_SOURCE=2 in GCC 4.3.3 ebuild.
i see no need to spam toolchain with this
IMO upstream should be allowed to add -Werror to CFLAGS if they want to. This shows upstream commitment to keep their source tree clean.
Could that break the compilation on newer gcc versions? Of course!
Should we ignore the warnings instead of fixing the code? I think not!
Upstream should use -Werror _during development_, not in release. In release it'll be a waste of time for users.
If GCC adds a warning in version 4.4 "foo bar will be removed from version 4.5", you want NOT to ignore it but also not want to make it fail before. It's a _warning_ for a good reason.
Please read http://blog.flameeyes.eu/2009/02/25/future-proof-your-code-dont-use-werror where I already discussed the problem.