From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22924 invoked by alias); 3 Mar 2010 17:53:43 -0000 Received: (qmail 22908 invoked by uid 22791); 3 Mar 2010 17:53:41 -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-ew0-f212.google.com (HELO mail-ew0-f212.google.com) (209.85.219.212) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 03 Mar 2010 17:53:33 +0000 Received: by ewy4 with SMTP id 4so1169253ewy.8 for ; Wed, 03 Mar 2010 09:53:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.93.79 with SMTP id k57mr730024wef.161.1267638810585; Wed, 03 Mar 2010 09:53:30 -0800 (PST) In-Reply-To: <83sk8h2tum.fsf@gnu.org> References: <20100301170152.GA20106@intel.com> <6dc9ffc81003021101yf91df69nddd08a824f777641@mail.gmail.com> <83y6ia30nc.fsf@gnu.org> <6dc9ffc81003021306s7cf79ef5n1069d8dcc994a3c6@mail.gmail.com> <83vdde2y6g.fsf@gnu.org> <20100302215235.GA3894@caradoc.them.org> <4B8D89CD.5050700@vmware.com> <6dc9ffc81003021359h15250892q139c4cac09d5cb88@mail.gmail.com> <6dc9ffc81003021407l27b513cbm288d1fd1e43d0c46@mail.gmail.com> <83sk8h2tum.fsf@gnu.org> Date: Wed, 03 Mar 2010 17:53:00 -0000 Message-ID: <6dc9ffc81003030953o3b77f457w4a2f648a96aa2534@mail.gmail.com> Subject: Re: PATCH: Support x86 pseudo registers From: "H.J. Lu" To: Eli Zaretskii Cc: msnyder@vmware.com, gdb-patches@sourceware.org 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/msg00109.txt.bz2 On Wed, Mar 3, 2010 at 9:33 AM, Eli Zaretskii wrote: >> Date: Tue, 2 Mar 2010 14:07:41 -0800 >> From: "H.J. Lu" >> Cc: Eli Zaretskii , gdb-patches@sourceware.org >> >> >>> I presume it lets us say $ah or $ax in addition to $eax, and lets $e= ax >> >>> work on 64-bit systems where we really have $rax. >> >> >> >> Mmm hmm, and the context would be expressions or anywhere where a >> >> register name is appropriate (eg. info reg). =A0Yes? >> >> >> > >> > Yes. >> > >> > (top-gdb) info reg $edi >> > edi =A0 =A0 =A0 =A0 =A0 =A00x1 =A0 =A0 =A01 >> > (top-gdb) info reg $rdi >> > rdi =A0 =A0 =A0 =A0 =A0 =A00x1 =A0 =A0 =A01 >> > (top-gdb) info reg $dl >> > dl =A0 =A0 =A0 =A0 =A0 =A0 0xd8 =A0 =A0 -40 >> > (top-gdb) info reg $dil >> > dil =A0 =A0 =A0 =A0 =A0 =A00x1 =A0 =A0 =A01 >> > (top-gdb) >> > >> > >> >> Basically, you can access any byte/word/dword registers, as shown >> in assembly code, the same way as word/dword registers. > > Then how about this entry: > > =A0* X86 general purpose registers > > =A0 GDB now supports reading/writing byte, word and double-word x86 > =A0 general purpose registers directly. =A0This means you can use, say, > =A0 $ah or $ax to refer, respectively, to the byte register AH and > =A0 16-bit word register AX that are actually portions of the 32-bit > =A0 register EAX or 64-bit register RAX. > > It looks good to me. Thanks. --=20 H.J.