No warning of violating strict aliasing rule and produce wrong code

[Andrew Haley]

Bingfeng Mei wrote:
> Sorry, I made a mistake. My local copy of mainline version (still 4.3.0
> 20080213) doesn't gave warning. I just updated my mainline GCC and it
> does give warning now. 

I think that you'll find the release 4.3 version does too.

While we try to ensure that gcc warns whenever it can about incorrect pointer
conversions, we certainly don't do so in all cases, and the general case is,
I suspect, incomputable.


Andrew.