public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-423-gd467030 Date: Wed, 07 Jul 2010 10:13:00 -0000 [thread overview] Message-ID: <20100707101337.30660.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 d46703098a8d64465c399fee375efa1fdfb20f04 (commit) from 8ae9ca7920537f3ee1e6826cbe475f7fa72d3fe3 (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 d46703098a8d64465c399fee375efa1fdfb20f04 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Jul 7 11:01:43 2010 +0200 Only include unwaddr in context for ia64. Not used on any other arch. * translate.cxx (c_unparser::emit_common_header): Don't add unwaddr field to context struct except for ia64. * tapsets.cxx (common_probe_entryfn_prologue): Only initialized unwaddr on ia64. (dwarf_derived_probe::emit_probe_local_init): Only call bspcache on ia64. * runtime/regs-ia64.c: Don't define (empty) bspcache for other arches. ----------------------------------------------------------------------- Summary of changes: runtime/regs-ia64.c | 4 ---- tapsets.cxx | 4 ++++ translate.cxx | 2 ++ 3 files changed, 6 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-07-07 10:13 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=20100707101337.30660.qmail@sourceware.org \ --to=mark@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).