public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "hunt at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2307] binary tracing
Date: Tue, 21 Feb 2006 08:43:00 -0000	[thread overview]
Message-ID: <20060221084301.24191.qmail@sourceware.org> (raw)
In-Reply-To: <20060209035522.2307.fche@redhat.com>


------- Additional Comments From hunt at redhat dot com  2006-02-21 08:43 -------
Both proposals require some changes to the transport interface to improve
efficiency. It will also improve performance of printf to have our own optimized
copy of vsnprintf() instead of using the kernel version.  Adding binary support
to that will be trivial. So I can add binary support to printf and if we change
our minds later and want to try the other way, we haven't really wasted any time.

I'll get started on it.



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED


http://sourceware.org/bugzilla/show_bug.cgi?id=2307

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

      parent reply	other threads:[~2006-02-21  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  3:55 [Bug translator/2307] New: " fche at redhat dot com
2006-02-17  6:53 ` [Bug translator/2307] " guanglei at cn dot ibm dot com
2006-02-17 10:55 ` hiramatu at sdl dot hitachi dot co dot jp
2006-02-17 15:32 ` guanglei at cn dot ibm dot com
2006-02-19  5:01 ` jrs at us dot ibm dot com
2006-02-20  3:00 ` fche at redhat dot com
2006-02-21  8:43 ` hunt at redhat dot com
2006-02-21  8:43 ` hunt at redhat dot com [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=20060221084301.24191.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).