From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13018 invoked by alias); 6 Oct 2011 20:11:18 -0000 Received: (qmail 13008 invoked by uid 22791); 6 Oct 2011 20:11:16 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 06 Oct 2011 20:11:03 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 4D2DF2BB451; Thu, 6 Oct 2011 16:11:03 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vKIOyfRcYvg1; Thu, 6 Oct 2011 16:11:03 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 1F1962BB44F; Thu, 6 Oct 2011 16:11:03 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id D284C145615; Thu, 6 Oct 2011 16:10:53 -0400 (EDT) Date: Thu, 06 Oct 2011 20:11:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [RFA/RFC] Restore old handling of multi-register variables Message-ID: <20111006201053.GS19246@adacore.com> References: <1317675787-7351-1-git-send-email-brobecker@adacore.com> <201110061854.52856.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201110061854.52856.pedro@codesourcery.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-10/txt/msg00180.txt.bz2 > This is a bit a step backwards in that it doesn't allow > marking parts of the value as unavailable when the type > is longer than one register. get_frame_register_value > was invented to allow for partially available registers. I understand. The bummer part is that I'm entering my busiest time of the year, and I haven't followed all this close enough to whip up a quick fix. So I'll keep that on my list to look at. Note that AVR will have to remain completely broken. We'll just have to add a note if we release 7.4 with that problem. -- Joel