From: "Jim Blandy" <jimb@red-bean.com>
To: "andrzej zaborowski" <balrogg@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Disallow pseudo-registers in agent expression.
Date: Tue, 05 Feb 2008 19:16:00 -0000 [thread overview]
Message-ID: <8f2776cb0802051116g1545efe1ld0d34dc602a8dd22@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0802051022h6b976c99se22127748d070440@mail.gmail.com>
On Feb 5, 2008 10:22 AM, andrzej zaborowski <balrogg@gmail.com> wrote:
> As far as I understand it's still a change that requires implementing
> new bits in architecture code, because architectures don't know how to
> make bytecode for pseudo-registers right now.
That's right. The suggested patch I posted doesn't show this, but the
way to do it would be to make it a gdbarch method with a predicate
indicating whether the architecture provides the method or not (an 'M'
entry in gdbarch.sh; search for "M -> " in there for docs), and then
have ax-gdb.c check for the presence of the method, use it if present,
and throw an error otherwise. This would allow us to implement the
method only on the architectures on which some contributor was
motivated to implement it.
> Apart from little time I have zero knowledge about 95% of the
> architectures in gdb :(
Well, there are a lot of architectures. I think many of our
contributors know only a few.
prev parent reply other threads:[~2008-02-05 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 19:09 andrzej zaborowski
2008-01-26 19:15 ` andrzej zaborowski
2008-01-27 21:11 ` Jim Blandy
2008-01-29 0:19 ` andrzej zaborowski
2008-01-29 1:49 ` Jim Blandy
2008-02-05 15:34 ` Jim Blandy
2008-02-05 15:58 ` Jim Blandy
2008-02-05 16:07 ` Jim Blandy
2008-02-05 18:23 ` andrzej zaborowski
2008-02-05 19:16 ` Jim Blandy [this message]
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=8f2776cb0802051116g1545efe1ld0d34dc602a8dd22@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=balrogg@gmail.com \
--cc=gdb-patches@sources.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