From a96681aaee89f85afacb8172be5ca6dd3342f9c0 Mon Sep 17 00:00:00 2001 From: Dorit Nuzman Date: Tue, 30 Oct 2007 05:25:10 +0000 Subject: re PR target/32893 (zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize) PR tree-optimization/32893 * tree-vectorize.c (vect_can_force_dr_alignment_p): Check STACK_BOUNDARY instead of PREFERRED_STACK_BOUNDARY. From-SVN: r129764 --- gcc/tree-vectorizer.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) (limited to 'gcc/tree-vectorizer.c') diff --git a/gcc/tree-vectorizer.c b/gcc/tree-vectorizer.c index 29acfac..43b51a7 100644 --- a/gcc/tree-vectorizer.c +++ b/gcc/tree-vectorizer.c @@ -1606,12 +1606,9 @@ vect_can_force_dr_alignment_p (const_tree decl, unsigned int alignment) if (TREE_STATIC (decl)) return (alignment <= MAX_OFILE_ALIGNMENT); else - /* This is not 100% correct. The absolute correct stack alignment - is STACK_BOUNDARY. We're supposed to hope, but not assume, that - PREFERRED_STACK_BOUNDARY is honored by all translation units. - However, until someone implements forced stack alignment, SSE - isn't really usable without this. */ - return (alignment <= PREFERRED_STACK_BOUNDARY); + /* This used to be PREFERRED_STACK_BOUNDARY, however, that is not 100% + correct until someone implements forced stack alignment. */ + return (alignment <= STACK_BOUNDARY); } -- cgit v1.1