On 29 February 2012 23:58, Glenn Fowler <[email protected]> wrote: > > you have to cut package maintainers some slack > I can point to at least a dozen places in the ast Makefiles > that contain workarounds that disable optimization for specific source files > and compilers
Do you have a list of such locations and entries in a bug database to track them? > there may be similar issues for other -f* style options as they themselves > get exercised > > we are not going to change working code for (currently) non-default options Our trouble is that ANSI/ISO C99 mandates strict aliasing rules. They are enabled by default, e.g. gcc 4.x defaults to -fstrict-aliasing. The warning which reports strict aliasing issues [-Wstrict-aliasing] is not enabled by default but your code is still silently compiled with strict aliasing rules. > without understanding all the issues > especially when that code (for ast mostly vmalloc) is at the heart of the > rest of the sw I understand. But right now, with AST compiled as C99 or C2011 code, the vmalloc code breaks because of the strict aliasing rules being enforced by *default*. No extra compiler options required to cause the breakage. Ced -- Cedric Blancher <[email protected]> Institute Pasteur _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
