> >> It might not be the best way but works so far. I'm no sure in particular >> about -fno-strict-aliasing and -fwrapv. Maybe allowing user to override >> these will break something subtly. > > Those two are a constant source of frustration :( I think we can best > ignore them for now, as they're causing trouble either way: even providing > them by default in the platform Makefiles can be problematic (see Haiku).
Please note that these two options are required. I had cases where strict aliasing caused code to fail and -fwrapv disables some questionable optimizations with regard to signed integer overflow. C compilers get more and more aggressive, cutting corners wherever possible by exploiting undefined (but not necessarily unreaasonable) behaviour. felix _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
