public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.1-109-gc7005ee
Date: Wed, 24 Feb 2010 01:49:00 -0000	[thread overview]
Message-ID: <20100224014949.7122.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  c7005ee1ba902de01a8863661a2031bfd45d3d40 (commit)
       via  30263a7389d5c2712536b74656193708bbc64d49 (commit)
      from  10328bcf86d49e5de83c5b22890204b5874740a9 (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 c7005ee1ba902de01a8863661a2031bfd45d3d40
Merge: 30263a7389d5c2712536b74656193708bbc64d49 10328bcf86d49e5de83c5b22890204b5874740a9
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Tue Feb 23 20:38:56 2010 -0500

    Merge branch 'master' of ssh://sources.redhat.com/git/systemtap
    
    * 'master' of ssh://sources.redhat.com/git/systemtap:
      PR10719 part 1: Partial constant folding
      Simplify null_statement construction
      Fixed PR 11269 by properly handling mmap syscall 'fd' argument.
      Removed rvalue operator check.
      PR 10690 (partial fix).  Handle '.=' operator in procfs probes.
    
    Conflicts:
    	tapsets.h

commit 30263a7389d5c2712536b74656193708bbc64d49
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Tue Feb 23 20:31:00 2010 -0500

    PR11005: @defined($tvar) predicate, part 1
    
    * staptree.h (defined_op): New class.
    * all files: Extend all visitors as appropriate, mostly
      dummy/pass-through implementation.
    * parse.cxx (parse_target_symbol): New function, factored out
      of parse_symbol().
      (parse_define_op): New function.
    * NEWS: Mention it.
    * parse.h: Corresponding changes.
    * tapsets.cxx (var_expanding_visitor::visit_defined_op):
      Implement @defined() semantics.
      (dwarf_var_expanding_visitor::visit_target_symbol): Adjust.
    * tapset-utrace.c (visit_target_symbol_arg): Avoid crashes
      on $argZZZ.
    * tapsets.cxx (sdt_var_expanding_visitor): Ditto.
    * semok/thirtysix.stp: New test.

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

Summary of changes:
 NEWS                          |    4 ++
 elaborate.cxx                 |   26 +++++++++
 elaborate.h                   |    1 +
 parse.cxx                     |  117 +++++++++++++++++++++++------------------
 parse.h                       |    4 +-
 staptree.cxx                  |   49 +++++++++++++++++
 staptree.h                    |   22 ++++++--
 tapset-utrace.cxx             |   10 +++-
 tapsets.cxx                   |   98 +++++++++++++++++++++++++++++++++--
 tapsets.h                     |    4 +-
 testsuite/semok/thirtysix.stp |   19 +++++++
 translate.cxx                 |   12 ++++-
 12 files changed, 302 insertions(+), 64 deletions(-)
 create mode 100755 testsuite/semok/thirtysix.stp


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


                 reply	other threads:[~2010-02-24  1:49 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=20100224014949.7122.qmail@sourceware.org \
    --to=fche@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).