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.3-306-g1beba84
Date: Fri, 19 Nov 2010 05:31:00 -0000	[thread overview]
Message-ID: <20101119053141.21694.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  1beba84157d0ef112ba1188db110b6f0e5879d66 (commit)
       via  75a371ce5d6bc65613edc9d4f475c4de516b68be (commit)
       via  7c15538e266a45590dd0e90b3eed1e53c18b9a5e (commit)
       via  b0c986b603eb96ec2af08d613bc97acb664b37a8 (commit)
       via  cda117193e340f81ac5f23b66e261ed6381d80b5 (commit)
      from  ea527496fe49207f29923f6b42ff5cba9170d6c0 (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 1beba84157d0ef112ba1188db110b6f0e5879d66
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Nov 18 20:42:33 2010 -0800

    sdt_types: remove manual type-casting
    
    For now, remove the int() and short() typecasting, as it seems to be
    working without.  We should try as much as possible to fix these issues
    in the translator and/or sdt.h before masking it in the test.

commit 75a371ce5d6bc65613edc9d4f475c4de516b68be
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Nov 18 20:06:52 2010 -0800

    Cast the proper sign and size of SDT constant args
    
    * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol):
      For the constant case, we still need to do some typecasting, as gcc
      doesn't necessarily match the sign of the constant to the type.

commit 7c15538e266a45590dd0e90b3eed1e53c18b9a5e
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Nov 18 19:32:56 2010 -0800

    Cast the proper sign and size of SDT register args
    
    * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol):
      For the REGISTER case, insert a typecast to deal with truncation and
      sign-extension of the argument as needed.

commit b0c986b603eb96ec2af08d613bc97acb664b37a8
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Nov 18 19:16:57 2010 -0800

    sdt_types: Use direct array args rather than &array when possible

commit cda117193e340f81ac5f23b66e261ed6381d80b5
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Nov 18 16:20:48 2010 -0800

    sdt_types: add a PASS statement for bitfields_small_var

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

Summary of changes:
 tapsets.cxx                            |   30 +++++++++++++++++++++++++++-
 testsuite/systemtap.base/sdt_types.c   |   10 +++++++-
 testsuite/systemtap.base/sdt_types.stp |   33 ++++++++++++-------------------
 3 files changed, 49 insertions(+), 24 deletions(-)


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


                 reply	other threads:[~2010-11-19  5:31 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=20101119053141.21694.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).