public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mahatma at eu dot by" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/41156] [4.4/4.5 Regression] zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize Date: Sat, 10 Oct 2009 13:48:00 -0000 [thread overview] Message-ID: <20091010134817.24188.qmail@sourceware.org> (raw) In-Reply-To: <bug-41156-682@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2009-10-10 13:48 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-08-24 15:56 [Bug target/41156] New: " hjl dot tools at gmail dot com 2009-08-25 10:20 ` [Bug target/41156] " mahatma at eu dot by 2009-08-25 15:52 ` jsm28 at gcc dot gnu dot org 2009-08-31 8:11 ` jakub at gcc dot gnu dot org 2009-08-31 13:52 ` hjl dot tools at gmail dot com 2009-08-31 21:48 ` mmitchel at gcc dot gnu dot org 2009-08-31 22:26 ` hjl dot tools at gmail dot com 2009-09-01 9:28 ` jakub at gcc dot gnu dot org 2009-09-01 13:20 ` hjl dot tools at gmail dot com 2009-09-08 12:09 ` mahatma at eu dot by 2009-09-19 16:12 ` mahatma at eu dot by 2009-09-19 21:42 ` hjl dot tools at gmail dot com 2009-09-25 11:03 ` mahatma at eu dot by 2009-10-09 14:07 ` mahatma at eu dot by 2009-10-09 14:09 ` mahatma at eu dot by 2009-10-09 14:09 ` mahatma at eu dot by 2009-10-09 14:10 ` mahatma at eu dot by 2009-10-09 14:11 ` mahatma at eu dot by 2009-10-09 14:39 ` mahatma at eu dot by 2009-10-09 14:41 ` mahatma at eu dot by 2009-10-09 14:44 ` hjl dot tools at gmail dot com 2009-10-10 13:48 ` mahatma at eu dot by [this message] 2009-10-10 13:51 ` mahatma at eu dot by 2009-10-10 14:46 ` hjl dot tools at gmail dot com 2009-10-12 11:41 ` mahatma at eu dot by 2009-10-12 14:00 ` hjl dot tools at gmail dot com 2009-10-12 22:48 ` dirtyepic at gentoo dot org 2009-10-13 12:16 ` mahatma at eu dot by 2009-10-13 13:26 ` mahatma at eu dot by 2009-10-15 12:58 ` jakub at gcc dot gnu dot org 2009-11-27 12:46 ` mahatma at eu dot by 2009-11-27 12:49 ` mahatma at eu dot by 2009-11-27 12:51 ` mahatma at eu dot by 2010-01-21 13:16 ` jakub at gcc dot gnu dot org 2010-02-17 16:49 ` mmitchel at gcc dot gnu dot org 2010-02-17 17:09 ` hjl dot tools at gmail dot com 2010-02-17 17:24 ` joseph at codesourcery dot com 2010-02-17 19:31 ` jakub at gcc dot gnu dot org 2010-04-30 8:57 ` [Bug target/41156] [4.4/4.5/4.6 " jakub at gcc dot gnu dot org 2010-06-10 19:08 ` phmagic at mail dot ru 2010-06-10 21:29 ` ed at catmur dot co dot uk 2010-06-11 1:43 ` phmagic at mail dot ru
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20091010134817.24188.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).