public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-133-g29bb0bb Date: Wed, 21 Oct 2009 23:59:00 -0000 [thread overview] Message-ID: <20091021235913.1236.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 29bb0bbc8603edb20de09e79fd8addb4a174947d (commit) from 1d2cd5ff6a8ff79b09e342a5907b29b4c340a9a5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 29bb0bbc8603edb20de09e79fd8addb4a174947d Author: Josh Stone <jistone@redhat.com> Date: Wed Oct 21 16:15:58 2009 -0700 Refactor probe locking into shared functions For scripts with thousands of probes, we save a fair amount of code-gen time in pass-4 by having the common locking code extracted into shared functions. * runtime/probe_lock.h (stp_lock_probe, stp_unlock_probe): New. * translate.cxx (c_unparser::emit_lock_decls): New, emits a static const array of locks needed for each probe. (c_unparser::emit_locks): Just call stp_lock_probe. (c_unparser::emit_unlocks): Just call stp_unlock_probe. ----------------------------------------------------------------------- Summary of changes: runtime/probe_lock.h | 68 +++++++++++++++++++++++++ translate.cxx | 133 ++++++++++++++++--------------------------------- 2 files changed, 112 insertions(+), 89 deletions(-) create mode 100644 runtime/probe_lock.h hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-10-21 23:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091021235913.1236.qmail@sourceware.org \ --to=jistone@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.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: linkBe 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).