Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support target specific qSupported
Date: Wed, 03 Feb 2010 19:06:00 -0000	[thread overview]
Message-ID: <6dc9ffc81002031106i61e6c7ceh46c8eb2dda31812f@mail.gmail.com> (raw)
In-Reply-To: <20100203190334.GA17498@caradoc.them.org>

On Wed, Feb 3, 2010 at 11:03 AM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Wed, Feb 03, 2010 at 10:59:14AM -0800, H.J. Lu wrote:
>> I am working x86 target descriptions. MMX is alias of ST. How do
>> I do it?
>
> You have many options.  One is to never describe the MMX registers
> explicitly.  Make them pseudo-registers.  This is how ARM NEON
> single-precision registers work.

I will give it a try.

> Aren't they pseudos already?  You may not have to do anything
> special.
>

x86 has ah, al, ax, eax, rax and will have xmm and ymm.  Is there a way to
support them, like

(gdb) p $ax
(gdb) p $ah

Thanks.



-- 
H.J.


  reply	other threads:[~2010-02-03 19:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03  4:03 H.J. Lu
2010-02-03  7:04 ` Hui Zhu
2010-02-03 13:59 ` Daniel Jacobowitz
2010-02-03 14:05   ` H.J. Lu
2010-02-03 14:15     ` Tristan Gingold
2010-02-03 14:26       ` H.J. Lu
2010-02-03 14:22     ` Daniel Jacobowitz
2010-02-03 14:34       ` H.J. Lu
2010-02-03 14:46         ` Daniel Jacobowitz
2010-02-03 15:08           ` H.J. Lu
2010-02-03 15:31             ` Daniel Jacobowitz
     [not found]             ` <20100203152350.GA1580@caradoc.them.org>
2010-02-03 16:44               ` H.J. Lu
2010-02-03 17:57                 ` Daniel Jacobowitz
2010-02-03 18:31                   ` H.J. Lu
2010-02-03 18:59             ` H.J. Lu
2010-02-03 19:03               ` Daniel Jacobowitz
2010-02-03 19:06                 ` H.J. Lu [this message]
2010-02-03 19:17                   ` Daniel Jacobowitz
2010-02-03 19:09                 ` Mark Kettenis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6dc9ffc81002031106i61e6c7ceh46c8eb2dda31812f@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox