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 14:05:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002030605k6eadda3me45828f7c8c6a362@mail.gmail.com> (raw)
In-Reply-To: <20100203135848.GA27938@caradoc.them.org>
On Wed, Feb 3, 2010 at 5:58 AM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Tue, Feb 02, 2010 at 08:03:39PM -0800, H.J. Lu wrote:
>> Hi,
>>
>> Intel AVX has 256bit YMM registers. XMM registers from SSE are the
>> aliases of the lower 128bit YMM registers. gdbserver on AVX machine
>> may use 256bit vector registers, instead of 128bit vector registers,
>> in the g/G packet. When gdb talks to gdbserver, they need to negotiate
>> to find out the maxium common register size supported by both gdb and
>> gdbserver. I added `x86:xstate=BYTES:xcr0=VALUE' to qSupported:
>
> Have you seen the Target Descriptions chapter in the manual? This is
> exactly what it was designed to do.
>
Which gdb target does similar things I need for AVX?
Thanks.
--
H.J.
next prev parent reply other threads:[~2010-02-03 14:05 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 [this message]
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
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=6dc9ffc81002030605k6eadda3me45828f7c8c6a362@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