------- Comment #17 from tromey at gcc dot gnu dot org 2007-01-17 01:32 ------- A flag to control the warning does not provide fine enough granularity of control. That is, sometimes the warning is appropriate, and disabling the warning would let through code that you would prefer not to let through.
One idea would be to disable the warning if the expression involves types which came from a template instantiation (sorry, I don't know the C++ terminology for this). This at least would suitably solve the case I ran into while writing gcjx. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11856
