This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/41156] [4.4/4.5 Regression] zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize
- From: "mahatma at eu dot by" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Oct 2009 13:48:17 -0000
- Subject: [Bug target/41156] [4.4/4.5 Regression] zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize
- References: <bug-41156-682@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from mahatma at eu dot by 2009-10-10 13:48 -------
(In reply to comment #19)
> Without a testcase, people may not review the patch.
>
May be just include your tests from Bug 40838? (even without testing)
>From http://gcc.gnu.org/bugzilla/attachment.cgi?id=18656
Your suggestions?
I understand so there are same results with your gcc-4.4-pr40838-*.patch, but
realigning whole code and exclude "misaligned" AMD CPUs. And warrantied to
realign in any place.
Your gcc-4.4-pr40838-3.patch lost realigning in unknown place - runtime
segfaults in Seamonkey. *-4.patch I don't test becouse alredy use simple
"-mstackrealign" solution - first there are dummy testing - surfing with
Seamonkey until sometimes segfault, second - I got new desktop with Athlon (but
was alredy satisfyed by "-mstackrealign" on old Celeron). Now I prefer to use
safe "-mstackrealign" solution for Intel CPUs on 32bit servers and to be sure
in safe SSE code. And see no visual defferences in perfomance whith global
"-mstackrealign".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41156