gcc3 vs 176.gcc

[Joseph S. Myers]

On Thu, 10 Jan 2002, Joe Buck wrote:

> Maybe this one should be a hard error if -fstrict-aliasing is enabled
> and optimization is on, as bad code is so highly likely.  But there
> is perhaps a philosophical problem with having a warning become an
> error based on optimization level.

Making it an error is no good since we don't know that any particular
function ever gets executed.  (You could compile it into a call to
abort(), though.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk