From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4998 invoked by alias); 25 Jul 2007 20:43:22 -0000 Received: (qmail 4970 invoked by uid 48); 25 Jul 2007 20:43:12 -0000 Date: Wed, 25 Jul 2007 20:43:00 -0000 Message-ID: <20070725204312.4969.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/32893] zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dorit at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg02605.txt.bz2 ------- Comment #1 from dorit at gcc dot gnu dot org 2007-07-25 20:43 ------- thanks a lot for checking both patches! > With this patch zlib appears to compile successfully. The loop is > vectorized with an "alignment of access forced using peeling" note and linked > apps no longer segfault. I'd like to try to verify if the problem is indeed related to the STACK_BOUNDARY, or whether this has to do with some weird interplay with the compilation of some other function, possibly after inlining (i.e. something like what we had in PR27770). I'm not sure how to suggest to check that... > I also tested using Andrew's patch from bug #16660 and always returning true in > vect_can_force_dr_alignment_p but it does not fix this error. Andrew, makes sense to you? > Let me know if I can provide any other info that would be useful to you. thanks, I'll think about it... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32893