public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: serhei@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-211-g49b68a3 Date: Mon, 27 Aug 2012 18:20:00 -0000 [thread overview] Message-ID: <20120827182022.2874.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 49b68a331e3c9e8eba92ee10297092c00c4b0579 (commit) from 1f631bc0444b05f1b44561e10c22fb4458682c03 (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 49b68a331e3c9e8eba92ee10297092c00c4b0579 Author: Serguei Makarov <smakarov@redhat.com> Date: Mon Aug 27 14:13:39 2012 -0400 PR14524: support old embedded-locals notation on a per-function basis Adding the pragma /* unmangled */ to an embedded-C function now enables the use of the pre-1.8 local names, i.e. THIS->n instead of STAP_ARG_n. This aids migration of pre-1.8 scripts and tapsets by allowing mixing two kinds of embedded functions (pre- and post-1.8) in the same code. ----------------------------------------------------------------------- Summary of changes: staptree.cxx | 6 +++++- staptree.h | 1 + translate.cxx | 40 ++++++++++++++++++++++++++++++++-------- translate.h | 2 +- 4 files changed, 39 insertions(+), 10 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-27 18:20 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=20120827182022.2874.qmail@sourceware.org \ --to=serhei@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).