This is the mail archive of the systemtap-cvs@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-387-g315bfa7


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  315bfa792075a6536432968285017e24cb6a8d0b (commit)
       via  6b1ea8e3a28f6ce61164e4b35a48c3a77a7623c0 (commit)
       via  cb034dff943fbd8eb93f9b137f7304b94fcceaa1 (commit)
      from  0cc10fbfeb41673ee516fc3c8eb94174c4aedc9c (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 315bfa792075a6536432968285017e24cb6a8d0b
Author: Josh Stone <jistone@redhat.com>
Date:   Fri May 20 18:41:39 2011 -0700

    PR12770: In loc2c, discontiguify based on total_bytes
    
    The total_bytes number is the part that really matters in determining
    whether a given dereference is greater than native size.  In particular,
    using loc->byte_size from a loc_address was telling us that 4 bytes is
    ok (sizeof pointer), even though the pointee was 8 total_bytes.
    
    * loc2c.c (discontiguify::pieces_small_enough): Compare total_bytes to
      the platform word size to decide whether to split into pieces.
      (discontiguify): For loc_constant, we have nothing to do as they're
      always copied byte-wise, but we should truncate the constant block to
      total_bytes.

commit 6b1ea8e3a28f6ce61164e4b35a48c3a77a7623c0
Author: Josh Stone <jistone@redhat.com>
Date:   Fri May 20 16:41:17 2011 -0700

    AUTHORS bump

commit cb034dff943fbd8eb93f9b137f7304b94fcceaa1
Author: Josh Stone <jistone@redhat.com>
Date:   Fri May 20 16:29:21 2011 -0700

    Let the @sum of an empty aggregate be 0
    
    It's handy to have a defined meaning for the @sum of empty aggregate, so
    one doesn't need to check for @count > 0 every time.  For example, now a
    pattern like "x += y; ... println(x)" can be more directly converted to
    aggregates with "x <<< y; ... println(@sum(x))".
    
    * translate.cxx (c_unparser::visit_stat_op): Let the @sum be read even
      on empty aggregates, but leaving the old behavior for compatibility.
    * testsuite/systemtap.maps/absentstats.exp: Check that both @count and
      @sum are allowed by default, and only @count for stap <= 1.4.
    * testsuite/systemtap.maps/ix_clear*.stp: Use @min for empty failure.

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

Summary of changes:
 AUTHORS                                  |    1 +
 loc2c.c                                  |   34 ++++++++---------------------
 testsuite/systemtap.maps/absentstats.exp |   23 +++++++++++++++++++-
 testsuite/systemtap.maps/absentstats.stp |   14 +++++++-----
 testsuite/systemtap.maps/ix_clear.stp    |    4 +-
 testsuite/systemtap.maps/ix_clear2.stp   |    4 +-
 testsuite/systemtap.maps/ix_clear3.stp   |    2 +-
 translate.cxx                            |    4 ++-
 8 files changed, 49 insertions(+), 37 deletions(-)


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]