From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: move agent opcodes to common file
Date: Thu, 17 Feb 2011 15:13:00 -0000 [thread overview]
Message-ID: <m31v363dek.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTi=-dJ8vjfUcF3cDoCFsX+pYs4YE1mcafhDNw1+6@mail.gmail.com> (Hui Zhu's message of "Thu, 17 Feb 2011 07:27:06 +0800")
>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>> And I have a question is if the common/ax.def updated, will the
>> ax-general.c, gdbserver/tracepoint.c and file that use the ax.h
>> rebuild?
Thanks -- I forgot to update the dependencies in gdbserver/Makefile.in.
Maybe I should finish my patch to convert gdbserver to automake :-)
gdb has automatic dependency tracking, so that part will just work.
>> I want try this patch with myself but looks your add the new op
>> aop_pick = 0x31, aop_rot = 0x32.
Yeah, it is based on my earlier patch. It is pretty easy to apply this
and fix the conflicts though.
>> BTW I have use the op 31 to be the op_printf in my printf patch and
>> kgtp new release version.
>> If your software(I think is SystemTap, right?) that use aop_pick =
>> 0x31, aop_rot = 0x32 is not release, could you let op_printf use the
>> op 31?
Sorry about that -- I meant to leave a gap for your opcode, but then I
forgot to actually do it. I fixed this locally.
While I am working on some SystemTap-related functionality, this patch
is independent from that.
This patch just lets us translate a few more DWARF opcodes to AX. Of
these, right now GCC only actually generates DW_OP_over. I just looked
at GCC and it seems that the current translation code does not handle
all the uses of DW_OP_over that GCC can emit.
Tom
next prev parent reply other threads:[~2011-02-17 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 22:25 Tom Tromey
2011-02-16 23:33 ` Hui Zhu
2011-02-17 2:06 ` Hui Zhu
2011-02-17 15:13 ` Tom Tromey [this message]
2011-02-18 19:11 ` Pedro Alves
2011-02-18 23:35 ` Tom Tromey
2011-02-20 15:06 ` Hui Zhu
2011-02-20 21:47 ` Pedro Alves
2011-02-21 8:17 ` Hui Zhu
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=m31v363dek.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@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