From: "Frank Ch. Eigler" <fche@redhat.com>
To: archer@sourceware.org, ppluzhnikov@google.com
Subject: Re: Improved linker-debugger interface
Date: Wed, 01 Jun 2011 01:24:00 -0000 [thread overview]
Message-ID: <20110601012341.GA7063@redhat.com> (raw)
Hi -
ppluzhnikov wrote:
> [...] One could hope that upstream glibc would adopt wide probes by
> default, but I would guess that chances of that actually happening
> are nil.
It depends. If it's out of the hot path, a five or eight-byte noop
may be OK. Measurements as to the actual impact would help.
- FChE
next reply other threads:[~2011-06-01 1:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 1:24 Frank Ch. Eigler [this message]
2011-06-02 23:56 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 15:37 Gary Benson
2011-05-25 18:21 ` Tom Tromey
2011-05-26 17:02 ` Gary Benson
2011-05-26 17:25 ` Tom Tromey
2011-05-26 17:37 ` Paul Pluzhnikov
2011-05-26 17:47 ` Tom Tromey
2011-05-26 21:07 ` Tom Tromey
2011-05-31 16:25 ` Gary Benson
2011-05-31 19:46 ` Tom Tromey
2011-05-31 20:41 ` Paul Pluzhnikov
2011-05-31 20:46 ` Tom Tromey
2011-05-31 21:05 ` Paul Pluzhnikov
2011-06-02 23:56 ` Tom Tromey
2011-06-07 16:58 ` Jan Kratochvil
2011-06-08 10:56 ` Gary Benson
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=20110601012341.GA7063@redhat.com \
--to=fche@redhat.com \
--cc=archer@sourceware.org \
--cc=ppluzhnikov@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).