From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15966 invoked by alias); 12 Mar 2010 18:22:27 -0000 Received: (qmail 15956 invoked by uid 22791); 12 Mar 2010 18:22:26 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Mar 2010 18:22:21 +0000 Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 7660313102; Fri, 12 Mar 2010 10:22:19 -0800 (PST) Received: from [10.20.124.100] (promd-2s-dhcp100.eng.vmware.com [10.20.124.100]) by jupiter.vmware.com (Postfix) with ESMTP id 6CB50DC328; Fri, 12 Mar 2010 10:22:19 -0800 (PST) Message-ID: <4B9A865B.4070000@vmware.com> Date: Fri, 12 Mar 2010 18:22:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: "H.J. Lu" CC: Pedro Alves , "gdb-patches@sourceware.org" , Eli Zaretskii Subject: Re: PATCH: Support x86 pseudo registers References: <20100301170152.GA20106@intel.com> <6dc9ffc81003021407l27b513cbm288d1fd1e43d0c46@mail.gmail.com> <83sk8h2tum.fsf@gnu.org> <201003120423.07852.pedro@codesourcery.com> <6dc9ffc81003112132h741284c3o65a33c9943be31c1@mail.gmail.com> In-Reply-To: <6dc9ffc81003112132h741284c3o65a33c9943be31c1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00469.txt.bz2 H.J. Lu wrote: > On Thu, Mar 11, 2010 at 8:23 PM, Pedro Alves wrote: >> On Wednesday 03 March 2010 17:33:21, Eli Zaretskii wrote: >>> * X86 general purpose registers >>> >>> GDB now supports reading/writing byte, word and double-word x86 >>> general purpose registers directly. This means you can use, say, >>> $ah or $ax to refer, respectively, to the byte register AH and >>> 16-bit word register AX that are actually portions of the 32-bit >>> register 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). I 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. I agree. I'm a user, and I'm very accustomed to typing "p $sp". I wouldn't like its meaning to change.