From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 503 invoked by alias); 13 Aug 2003 04:54:16 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 32639 invoked from network); 13 Aug 2003 04:54:14 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 13 Aug 2003 04:54:14 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h7D4sEt14419 for ; Wed, 13 Aug 2003 00:54:14 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h7D4s7L31915; Wed, 13 Aug 2003 00:54:07 -0400 Received: from dot.sfbay.redhat.com (dot.sfbay.redhat.com [172.16.24.7]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h7D4s6O21607; Tue, 12 Aug 2003 21:54:06 -0700 Received: (from rth@localhost) by dot.sfbay.redhat.com (8.11.6/8.11.6) id h7D4s5911927; Tue, 12 Aug 2003 21:54:05 -0700 X-Authentication-Warning: dot.sfbay.redhat.com: rth set sender to rth@redhat.com using -f Date: Wed, 13 Aug 2003 04:54:00 -0000 From: Richard Henderson To: Andrew Cagney Cc: Michal Ludvig , Daniel Jacobowitz , gdb Subject: Re: [testsuite & dwarf2] How to handle store.exp failure on AMD64? Message-ID: <20030813045405.GB11912@redhat.com> References: <3F3212B7.8060003@suse.cz> <20030807135035.GA28000@nevyn.them.org> <3F326928.3020502@redhat.com> <20030807150201.GA29511@nevyn.them.org> <3F3275EC.3000702@redhat.com> <3F32C75D.2010007@suse.cz> <3F39B678.70409@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F39B678.70409@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-08/txt/msg00134.txt.bz2 On Tue, Aug 12, 2003 at 11:54:32PM -0400, Andrew Cagney wrote: > I would have expected the CIE.INITIAL_INSTRUCTIONS to specify the > default state of all DWARF2 registers, and not just a select few. Folks already complain unwind info is too large. As I said, GCC's unwinder assumes DW_CFA_same_value unless otherwise stated. Since scratch registers aren't live across the call, it doesn't matter that we don't mark registers DW_CFA_undefined; any (accurate) debug information you'll find at the call site in the caller simply won't say that values are live in those registers. Anything else would be a bug. So assuming DW_CFA_same_value produces the most compact representation. r~