Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
Date: Mon, 04 Jun 2007 20:13:00 -0000	[thread overview]
Message-ID: <200706042013.l54KD3da002950@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070604200016.GD23516@caradoc.them.org> from "Daniel Jacobowitz" at Jun 04, 2007 04:00:16 PM

Daniel Jacobowitz wrote:
> On Sat, Jun 02, 2007 at 09:34:01PM +0200, Ulrich Weigand wrote:
> > Hello,
> > 
> > this patch makes the new "info spu" commands available via the GDB/MI
> > protocol.  The Cell Broadband Engine IDE is already able to make use
> > of these commands and display the SPU status information.
> > 
> > It looks like these are the first platform-specific MI commands, so
> > I'd appreciate opinions on this ...
> 
> The documentation doesn't say what the output should be; we need that
> for consumers to parse it usefully.  Does it get MI-tabulated?  If
> not, there's always -interpreter-exec.

It depends, some "info spu" commands return just a couple of values,
others return a table, yet others some values followed by a table.

I agree we need to document the format, at least provide examples.
Sorry for omitting that ...

> I mentioned in an earlier message that it would be nice if this sort
> of output was more generic, so that it could come straight from a
> target description file without a lot of tdep code.  That's easy to
> put off to another day, but the same thing applies to GDB's
> conversation with consumers.  Is there some less target-specific way
> that we can present this information?  For instance, a way that an IDE
> could automatically pick up all the target-specific data that GDB
> knows about without the IDE having to know about all of it also.
> 
> That doesn't mean the IDE can't know about it too, of course, to
> provide more specialized access.

That might be a good idea in general, but in this particular case,
preparing the data requires quite a bit of effort and knowledge of
the data format.  I'm not sure I'd want to describe the effects of,
say, info_spu_dma_cmdlist in XML.  I also want to avoid having to
duplicate that processing in GDB and the IDE ...

> If we do go ahead with these new commands I suggest you add a test
> case for them.

Right, sorry about that.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-06-04 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:34 Ulrich Weigand
2007-06-02 20:38 ` Eli Zaretskii
2007-06-03 13:29   ` Ulrich Weigand
2007-06-03 16:45     ` Eli Zaretskii
2007-06-04 20:00 ` Daniel Jacobowitz
2007-06-04 20:13   ` Ulrich Weigand [this message]
2007-06-04 20:22     ` Daniel Jacobowitz
2007-06-04 22:59       ` Ulrich Weigand
2007-06-05 11:12         ` Daniel Jacobowitz
2007-06-14 20:05           ` Ulrich Weigand
2007-06-21  2:23             ` Ricardo Marin Matinata
2007-06-21 22:22               ` Nick Roberts
2007-06-22 20:53               ` Jim Blandy
2007-06-20  0:28 Nick Roberts

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=200706042013.l54KD3da002950@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --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