From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7038 invoked by alias); 25 Jan 2010 08:22:46 -0000 Received: (qmail 7002 invoked by uid 48); 25 Jan 2010 08:22:34 -0000 Date: Mon, 25 Jan 2010 08:22:00 -0000 Message-ID: <20100125082234.7001.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/37022] internal compiler error: in compute_barrier_args_size 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: 2010-01/txt/msg02859.txt.bz2 ------- Comment #18 from jakub at gcc dot gnu dot org 2010-01-25 08:22 ------- It is no longer marged regression, so no longer release critical. Anyway, the goal should be to reenable the asserts in dwarf2out.c and fix the issues, because they really result in wrong unwind info. Only the unwinder uses it though (DW_CFA_GNU_args_size), so the question is if we can come up with a testcase that actually misbehaves of it. There are two known cases which triggered the assertions - one is alloca with an argument that ends up to be constant in the end, and the other is crossjumping of noreturn sequences with different stack push depth. -- jakub at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |major Priority|P1 |P2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022