[Bug driver/78772] -fstrict-aliasing should turn on Wstrict-aliasing automaticly

["ma.jiang at zte dot com.cn" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78772

--- Comment #4 from ma.jiang at zte dot com.cn ---
(In reply to Markus Trippelsdorf from comment #3)
> Please no. 
> There are many other cases where optimizations could introduce issues that
> you will not notice when you compile without warnings.
> Just use -Wall.

Hi, Markus 
  Thanks for your quick reply. I know the existence of both "Wall" and
"Wextra", And I  did use them when compiling my codes. But, there are many guys
do not know them. Moreover, As I see many open source projects does not use
them either. It is that OK to assume all gcc users know "Wall"?
  On the other side, creating a new mechanism to open warnings for dangerous
optimizations is not a hard work as I think. We just need to create a  table
which connect the optimization and corresponding warning.