From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26448 invoked by alias); 8 Mar 2009 14:37:45 -0000 Received: (qmail 26391 invoked by uid 48); 8 Mar 2009 14:37:32 -0000 Date: Sun, 08 Mar 2009 14:37:00 -0000 Message-ID: <20090308143732.26390.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: "amylaar 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-03/txt/msg00539.txt.bz2 ------- Comment #16 from amylaar at gcc dot gnu dot org 2009-03-08 14:37 ------- (In reply to comment #9) > The darwin -m64 failures are then the same problem, cross-jumping of noreturn > calls between different level of stack depths. > I've been wrong about DW_CFA_GNU_args_size being useless for cfa.reg != > STACK_POINTER_REGNUM, while such directives won't ever be used by the libgcc > unwinder, they might be used by debuggers to set correct value of stack > pointer, > and therefore such directives aren't useless and so we should avoid > crossjumping > in that case. It is a valid size optimization, so if the unwinder doesn't need the directive to be always correct, we should do this optimization for -Os unless you also specify -O1. Optimization levels above -O1 are known to give imperfect debug information. And -O1 defaults to -fno-crossjumping . -- amylaar at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amylaar at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37022