From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: partially available registers
Date: Mon, 18 Jul 2011 04:15:00 -0000 [thread overview]
Message-ID: <CAN9gPaGFQ7256zUxuG3chr3mgzve=ACVJca8pMn=_bPWPes4BQ@mail.gmail.com> (raw)
In-Reply-To: <m3sjq79soa.fsf@fleche.redhat.com>
On Fri, Jul 15, 2011 at 4:48 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>
> Daniel> As for the patch itself:
> Daniel> * Some documentation on the gdbarch method would be nice, in
> Daniel> particular, the return value. Does 0 mean "not a pseudo"?
>
> Yeah, I left that out for the initial change, but I think I shouldn't
> have.
>
> I find gdbarch.sh very hard to read. Does anybody else?
Incredibly. Someone please flip us to C++ and use a normal construct
for this...
--
Thanks,
Daniel
next prev parent reply other threads:[~2011-07-17 20:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 20:17 Tom Tromey
2011-07-14 4:24 ` Daniel Jacobowitz
2011-07-15 20:52 ` Tom Tromey
2011-07-18 4:15 ` Daniel Jacobowitz [this message]
2011-07-20 20:14 ` Pedro Alves
2011-07-20 18:49 ` Sergio Durigan Junior
2011-07-20 20:46 ` Tom Tromey
2011-07-20 20:53 ` Tom Tromey
2011-07-24 13:48 ` Mark Kettenis
2011-07-25 15:50 ` Tom Tromey
2011-07-21 5:23 ` Ulrich Weigand
2011-07-21 20:27 ` Tom Tromey
2011-07-22 13:48 ` Ulrich Weigand
2011-07-22 15:42 ` Tom Tromey
2011-07-22 14:30 ` Pedro Alves
2011-07-22 15:40 ` Tom Tromey
2011-07-22 19:10 ` Pedro Alves
2011-07-22 19:19 ` Tom Tromey
2011-07-22 19:31 ` Pedro Alves
2011-07-22 21:58 ` Pedro Alves
2011-07-22 22:20 ` Tom Tromey
2011-07-26 17:08 ` Pedro Alves
2011-07-26 17:13 ` Pedro Alves
2011-07-26 19:46 ` Tom Tromey
2011-07-27 18:25 ` Tom Tromey
2011-07-27 19:30 ` Tom Tromey
2011-07-27 19:33 ` Pedro Alves
2011-07-28 5:19 ` 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='CAN9gPaGFQ7256zUxuG3chr3mgzve=ACVJca8pMn=_bPWPes4BQ@mail.gmail.com' \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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