From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32452 invoked by alias); 12 Mar 2010 05:32:10 -0000 Received: (qmail 32436 invoked by uid 22791); 12 Mar 2010 05:32:09 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40 X-Spam-Check-By: sourceware.org Received: from mail-wy0-f169.google.com (HELO mail-wy0-f169.google.com) (74.125.82.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Mar 2010 05:32:05 +0000 Received: by wye20 with SMTP id 20so441139wye.0 for ; Thu, 11 Mar 2010 21:32:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.85.12 with SMTP id t12mr321600wee.158.1268371922676; Thu, 11 Mar 2010 21:32:02 -0800 (PST) In-Reply-To: <201003120423.07852.pedro@codesourcery.com> References: <20100301170152.GA20106@intel.com> <6dc9ffc81003021407l27b513cbm288d1fd1e43d0c46@mail.gmail.com> <83sk8h2tum.fsf@gnu.org> <201003120423.07852.pedro@codesourcery.com> Date: Fri, 12 Mar 2010 05:32:00 -0000 Message-ID: <6dc9ffc81003112132h741284c3o65a33c9943be31c1@mail.gmail.com> Subject: Re: PATCH: Support x86 pseudo registers From: "H.J. Lu" To: Pedro Alves Cc: gdb-patches@sourceware.org, Eli Zaretskii , msnyder@vmware.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00434.txt.bz2 On Thu, Mar 11, 2010 at 8:23 PM, Pedro Alves wrote: > On Wednesday 03 March 2010 17:33:21, Eli Zaretskii wrote: >> =A0* X86 general purpose registers >> >> =A0 =A0GDB now supports reading/writing byte, word and double-word x86 >> =A0 =A0general purpose registers directly. =A0This means you can use, sa= y, >> =A0 =A0$ah or $ax to refer, respectively, to the byte register AH and >> =A0 =A016-bit word register AX that are actually portions of the 32-bit >> =A0 =A0register EAX or 64-bit register RAX. >> > > I just realized that this change means that $sp is now just > a 16-bit word of $esp, instead of a pseudo-register resolving to > either $esp/$rsp (32-bit/64-bit). =A0I can't say it is actually wrong to > have it that way, but, I think this should at least be mentioned in > NEWS, if not in the manual too, because it can catch people > by surprise. > I think we should treat sp as a special case here and not to make it 16bit. --=20 H.J.