Melchior FRANZ wrote: > Now the question is: should fgfs work around a broken gcc release, > when there's hope that the next version will be fixed? Or is it not > a bug,
Strictly, it's not a bug. Within a single function, it is not legal to have two pointers of different types pointing to the same address. It never has been, AFAIK, but the gcc optimizer was never sophisticated enough to cause problems. It is now. :) Does adding --no-strict-aliasing to the CFLAGS fix the problem? Maybe we should consider that for the near term... Andy _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
