From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
Vyacheslav Egorov <vegorov@chromium.org>
Subject: Re: JIT interface slowness
Date: Mon, 03 Jan 2011 23:40:00 -0000 [thread overview]
Message-ID: <201101032340.29406.pedro@codesourcery.com> (raw)
In-Reply-To: <201101032332.28548.pedro@codesourcery.com>
On Monday 03 January 2011 23:32:18, Pedro Alves wrote:
> patches easier to read. (I just put "diff -up" in ~/.cvsup).
Err, I meant ~/.cvsrc.
--
Pedro Alves
next prev parent reply other threads:[~2011-01-03 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 19:43 Vyacheslav Egorov
2010-12-31 20:10 ` Pedro Alves
2010-12-31 21:39 ` Vyacheslav Egorov
2010-12-31 22:23 ` Pedro Alves
2010-12-31 23:12 ` Vyacheslav Egorov
2010-12-31 23:36 ` Pedro Alves
2011-01-02 7:54 ` Paul Pluzhnikov
2011-01-03 10:44 ` Vyacheslav Egorov
2011-01-03 17:32 ` Paul Pluzhnikov
2011-01-03 22:01 ` Paul Pluzhnikov
2011-01-03 23:32 ` Pedro Alves
2011-01-03 23:40 ` Pedro Alves [this message]
2011-01-03 23:47 ` Paul Pluzhnikov
2011-01-04 0:13 ` Pedro Alves
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=201101032340.29406.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=vegorov@chromium.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