From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15008 invoked by alias); 12 Mar 2010 18:20:21 -0000 Received: (qmail 14995 invoked by uid 22791); 12 Mar 2010 18:20:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Mar 2010 18:20:16 +0000 Received: (qmail 30398 invoked from network); 12 Mar 2010 18:20:14 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 12 Mar 2010 18:20:14 -0000 From: Pedro Alves To: gdb-patches@sourceware.org, Eli Zaretskii Subject: Re: PATCH: Support x86 pseudo registers Date: Fri, 12 Mar 2010 18:20:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-19-generic; KDE/4.3.2; x86_64; ; ) Cc: Daniel Jacobowitz , hjl.tools@gmail.com, msnyder@vmware.com References: <20100301170152.GA20106@intel.com> <20100312162949.GA22104@caradoc.them.org> <83d3z92ysk.fsf@gnu.org> In-Reply-To: <83d3z92ysk.fsf@gnu.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201003121820.10722.pedro@codesourcery.com> 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: 2010-03/txt/msg00468.txt.bz2 On Friday 12 March 2010 18:13:47, Eli Zaretskii wrote: > > Date: Fri, 12 Mar 2010 11:30:04 -0500 > > From: Daniel Jacobowitz > > Cc: Pedro Alves , gdb-patches@sourceware.org, > > hjl.tools@gmail.com, msnyder@vmware.com > > > > On Fri, Mar 12, 2010 at 06:04:45PM +0200, Eli Zaretskii wrote: > > > Maybe, but frankly I don't really understand what it says, exactly. > > > Does it mean that if the name does clash with the architecture, the > > > architecture's meaning is used? > > > > I think that's what was intended. > > Then maybe we should say when there's conflict, the generic name > _might_ be unavailable. > We could also stick to defaulting to the architecture meaning, and always provide $_pc, $_sp, $_fp, $_ps registers that always map to the generic versions. That way, when there's a conflict, there's always an escape route. -- Pedro Alves