This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/30819] php 5.2.1 / gcc 4.1.1 / solaris 2.9 / 64 bit



------- Comment #8 from tony2001 at php dot net  2007-02-16 14:16 -------
(In reply to comment #6)
> If the trigger happens to be -fstrict-aliasing, it's very likely a violation of
> the type-based aliasing rules of the C/C++ languages.  They are usually exposed
> by the scheduler, which is more aggressive on SPARC than on x86 for example.

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 ? 
(GCC 3.x works perfectly fine in the same time )


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30819


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]