From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32140 invoked by alias); 1 Sep 2009 09:28:46 -0000 Received: (qmail 31505 invoked by uid 48); 1 Sep 2009 09:28:21 -0000 Date: Tue, 01 Sep 2009 09:28:00 -0000 Message-ID: <20090901092821.31504.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/41156] [4.4/4.5 Regression] 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: "jakub 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: 2009-09/txt/msg00023.txt.bz2 ------- Comment #6 from jakub at gcc dot gnu dot org 2009-09-01 09:28 ------- IMHO either standard options compiled code shouldn't be called from -mpreferred-stack-boundary=2 code, or it needs to be compiled with -mincoming-stack-boundary=2. But it should be user's responsibility. Ensuring by default outgoing calls are 16 byte aligned, but not assuming it is just a very stupid thing to do and unnecessarily penalizes normal users. It is certainly not true that most code is compiled with -mpreferred-stack-boundary=2, only kernel and a handful of packages is by default, and kernel has its own ABI (and doesn't use FPU nor SSE*). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41156