From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1853 invoked by alias); 22 Aug 2009 12:09:41 -0000 Received: (qmail 1826 invoked by uid 48); 22 Aug 2009 12:09:28 -0000 Date: Sat, 22 Aug 2009 12:09:00 -0000 Message-ID: <20090822120928.1825.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/40718] Invalid code produced with -foptimize-sibling-calls In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "slyfox at inbox dot ru" 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-08/txt/msg01777.txt.bz2 ------- Comment #1 from slyfox at inbox dot ru 2009-08-22 12:09 ------- I can confirm gcc-4.4.1 errors the same way. I think stdcall is offender: My sample is more complicated, but has the same features: stdcall+tailcall. Produces SIGSEGV for me https://bugs.gentoo.org/show_bug.cgi?id=282189 -- slyfox at inbox dot ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slyfox at inbox dot ru http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40718