Brian Dessent wrote:
The best bet is to fix the invalid code. The next best thing is probably -fno-strict-aliasing. This is a frequent and somewhat sensitive topic on this mailing list, so I suggest you read the past threads, e.g. <http://www.google.com/search?num=100&q=site%3Agcc.gnu.org+inurl%3Aml+inurl%3A%22gcc-help%22+strict+aliasing+rules>. Brian
Thanks for this, the -fno-strict-aliasing has stopped the warnings. I asked here because the www.gcc.gnu.org server appears to be down.
