------- Comment #5 from acahalan at gmail dot com 2006-09-27 02:07 ------- (In reply to comment #4) > Except it is better just to fix your code for aliasing issues.
Yes, and all other bugs should be fixed as well. This is often impractical. Is there even one large modern kernel which is compiled with strict aliasing enabled? (not Linux, not FreeBSD, definitely not OpenBSD because they patch gcc to have a different default...) > The reason why > restrict does not work without strict aliasing is because it needs aliasing > sets and the only way to get that is with strict aliasing. Yes, exactly. That is the bug. Aliasing sets should be computed. The only affect of -fno-strict-aliasing should be to change how non-char data types are handled in that computation. The non-char types should be handled as char is normally. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29239
