From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23798 invoked by alias); 31 Jan 2007 12:49:34 -0000 Received: (qmail 23788 invoked by uid 22791); 31 Jan 2007 12:49:33 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 31 Jan 2007 12:49:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1HCEty-0004nE-KJ; Wed, 31 Jan 2007 07:49:26 -0500 Date: Wed, 31 Jan 2007 12:49:00 -0000 From: Daniel Jacobowitz To: Andreas Schwab Cc: gdb-patches@sourceware.org Subject: Re: Testsuite failures in gdb.base/callfuncs.exp Message-ID: <20070131124926.GA18380@nevyn.them.org> Mail-Followup-To: Andreas Schwab , gdb-patches@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00603.txt.bz2 On Wed, Jan 31, 2007 at 01:33:26PM +0100, Andreas Schwab wrote: > This fixes these testsuite failures on ia64: > > FAIL: gdb.base/callfuncs.exp: gdb function calls preserve register contents > FAIL: gdb.base/callfuncs.exp: continue after stop in call dummy preserves register contents > FAIL: gdb.base/callfuncs.exp: return after stop in call dummy preserves register contents > > The problem is that the bspstore register is specially tied with the bsp > register, and this can't be controlled by gdb. How does this work - i.e. how do we guarantee that the restored state is equivalent? Does it indicate extra registers written to the register stack? -- Daniel Jacobowitz CodeSourcery