From: Yao Qi <yao@codesourcery.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] JIT Debug info reader
Date: Fri, 01 Jul 2011 16:32:00 -0000 [thread overview]
Message-ID: <4E0DF69E.6000806@codesourcery.com> (raw)
In-Reply-To: <4E0DF2C3.2070109@playingwithpointers.com>
On 07/02/2011 12:16 AM, Sanjoy Das wrote:
> I am not familiar with dejagnu; I'll have a look and try to come up with
> some way this code can be tested.
>
It is just my thought. If you feel uncomfortable on dejagnu, please
feel free to ignore my comment on dejagnu. :)
> I'll incorporate the suggested changes and re-send a new patch set in a
> while (along with some dejagnu tests).
I think that is helpful to the right people (not me) to review, and
approve it, hopefully.
--
Yao (é½å°§)
prev parent reply other threads:[~2011-07-01 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:48 Sanjoy Das
2011-07-01 13:51 ` Yao Qi
2011-07-01 16:12 ` Sanjoy Das
2011-07-01 16:32 ` Yao Qi [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=4E0DF69E.6000806@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=sanjoy@playingwithpointers.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