From: Daniel Jacobowitz <dan@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support target specific qSupported
Date: Wed, 03 Feb 2010 14:46:00 -0000 [thread overview]
Message-ID: <20100203144626.GA31389@caradoc.them.org> (raw)
In-Reply-To: <6dc9ffc81002030634wd2976e5t2a42b639c455b850@mail.gmail.com>
On Wed, Feb 03, 2010 at 06:34:14AM -0800, H.J. Lu wrote:
> We have our own remote gdb stub, which needs to talk to both old gdb,
> which only understands SSE g/G packet, and new gdb, which understands
> AVX g/G packet. Does the target description support negotiation so
> that old gdb and new remote gdb stub can use SSE g/G packet?
The goal of target descriptions is to not need negotiation.
Everything is controlled by the target. But with older GDBs, because
x86 did not get target-described register support right away, there's
a problem.
I suggest adding something to the GDB-side qSupported packet saying
that AVX is OK. You don't need anything on the stub side of the
qSupported reply; you just need to reply to qXfer:features.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-02-03 14:46 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 [this message]
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=20100203144626.GA31389@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
/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