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.6-310-g720c435
Date: Thu, 13 Oct 2011 20:28:00 -0000	[thread overview]
Message-ID: <20111013202832.9628.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  720c435f4135efc9cef5d25cde1dd43cab88850d (commit)
      from  a4b9c3b3cf767f977c2ce15f25eb0fc9c1b53f42 (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 720c435f4135efc9cef5d25cde1dd43cab88850d
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Oct 13 13:22:29 2011 -0700

    PR13155: Fix tracepoint argument access
    
    The restructured tracepoint build broke the way tracepoint parameters
    are passed to the script.  This patch cleans that up, and simplifies a
    few other parts of the code generation.
    
    * tapsets.cxx (tracepoint_derived_probe_group::emit_module_decls):
      Define intptr_t for the aux source.  Collect .used entries from
      p->args[] into used_args[] to ease call-list generation. Simplify
      registration by replacing the wrappers with plain declarations.
    * buildrun.cxx (compile_pass): We do have everything needed for strict
      prototypes, so don't squash this warning.

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

Summary of changes:
 buildrun.cxx |    3 --
 tapsets.cxx  |   96 +++++++++++++++++++++++++++++-----------------------------
 2 files changed, 48 insertions(+), 51 deletions(-)


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


                 reply	other threads:[~2011-10-13 20:28 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=20111013202832.9628.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: 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).