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.7-319-g021b325
Date: Wed, 13 Jun 2012 17:30:00 -0000	[thread overview]
Message-ID: <20120613173013.17250.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  021b325105d29868d7aa1bc2d51a6906a1d5c1dd (commit)
      from  47ef763543a0b59640c26c31e7bc232a7b5ea43a (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 021b325105d29868d7aa1bc2d51a6906a1d5c1dd
Author: Serguei Makarov <smakarov@redhat.com>
Date:   Wed Jun 13 13:28:38 2012 -0400

    NEWS: describe the required changes to embedded-C functions.
    
    - SystemTap now mangles local variables to avoid collisions with C
      headers included by tapsets. This required a change in how
      embedded-C functions access local parameters and the return value slot.
    
      Instead of THIS->foo in an embedded-C function, please use the newly
      defined macro STAP_ARG_foo (substitute the actual name of the
      argument for 'foo'); instead of THIS->__retvalue, use the newly
      defined STAP_RETVALUE. All of the tapsets and test cases have been
      adapted to use this new notation.
    
      If you need to run code which uses the old THIS-> notation, run stap
      with the --compatible=1.7 option.

-----------------------------------------------------------------------

Summary of changes:
 NEWS |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2012-06-13 17:30 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=20120613173013.17250.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: 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).