------- Comment #9 from ebotcazou at gcc dot gnu dot org 2007-02-16 16:44 ------- > Do you mean it is some kind of "improvement" in GCC 4.x that makes the result > binary to segfault in random places when compiled without -fstrict-aliasing ?
No, -fstrict-aliasing is not new, it's there since GCC 2.95 and the rules haven't changed since then. But GCC 4 is much more aggressive than GCC 3 in some cases and this may uncover subtle aliasing violations in the code. See the section in the manual about -fstrict-aliasing. Or this could be a bug in the compiler. That's why it would be interesting to try with the 4.1.2 release too. In either case, someone familiar with the PHP code will have to determine what goes wrong exactly. Only then will we be able to find a remedy. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30819
