g++ no longer ignoring some warning flags?

[Jason Merrill]

>>>>> Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes:

 >> From: Jason Merrill <jason@cygnus.com>
 >>  
 >> >>>>> Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes
 >>  
 >>  >> We could issue warnings instead of errors, but being silent in that case
 >>  >> is not a good solution, IMHO.
 >>  
 >>  > A warning seems a good idea.
 >>  
 >> The gcc philosophy in the past has been to silently accept flags used by
 >> other frontends.  I'm not sure we want to change that.

 > Right, but g++ already *has* been changed to hard error in these
 > cases.

That was an unintended (I assume) side effect of Dave Brolley's change to
always pass args down to frontends.

Jason