public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: roland@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-128-g22ac618
Date: Wed, 15 Sep 2010 20:26:00 -0000	[thread overview]
Message-ID: <20100915202636.8440.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  22ac61865162e74823c869e011760805d46cfb32 (commit)
       via  1220de76265ef75bbd208e89ddc24713202b3955 (commit)
      from  6d892a15eac1f734d752dcb8ba348f07b6118ec5 (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 22ac61865162e74823c869e011760805d46cfb32
Author: Roland McGrath <roland@redhat.com>
Date:   Wed Aug 18 15:37:22 2010 -0700

    Test case for DW_OP_GNU_implicit_pointer support
    
    * testsuite/systemtap.base/implicitptr.c: New file.
    * testsuite/systemtap.base/implicitptr.stp: New file.
    * testsuite/systemtap.base/implicitptr.exp: New file.

commit 1220de76265ef75bbd208e89ddc24713202b3955
Author: Roland McGrath <roland@redhat.com>
Date:   Tue Jul 27 04:55:48 2010 -0700

    loc2c internal reorganization and DW_OP_GNU_implicit_pointer handling
    
    * loc2c.c (struct location_context): New type.
    (struct location): New member context points to that.
    Add pointer variant with .type = loc_implicit_pointer.
    (alloc_location): Take just context pointer as argument.
    (FAIL): Use context pointer.
    (new_context): New function.
    (translate_constant): New function, broken out of ...
    (c_translate_constant): ... here.  Call it.
    (new_synthetic_loc): Don't take pool argument, origin->context has it.
    (lose): Take new argument LEN, overall length of LEXPR.
    Don't mention the offset into LEXPR if LEXPR is NULL or I is past LEN.
    (translate): Take context argument instead of pool, addrbias.
    Handle DW_OP_GNU_implicit_pointer.
    (location_from_address): Take context argument instead of pool, fail,
    fail_arg, emit_address, dwbias, attr, address, fb_attr, cfa_ops.
    (location_from_attr): New function.
    (translate_offset): New function, broken out of ...
    (location_relative): ... here.  Call it.
    Take context argument instead of pool, dwbias, attr, address.
    (c_translate_location): Use new_context.
    (c_translate_argument): Likewise.
    (emit_base_fetch): Diagnose for loc_implicit_pointer.
    (emit_base_store): Likewise.
    (c_translate_addressof, c_translate_array): Likewise.
    (discontiguify): Likewise.  Take context argument instead of pool.
    (c_translate_pointer): Handle loc_implicit_pointer.
    (c_translate_array_pointer): Likewise.
    (c_emit_location): Likewise.

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

Summary of changes:
 loc2c.c                                  |  778 ++++++++++++++++++------------
 testsuite/systemtap.base/implicitptr.c   |   63 +++
 testsuite/systemtap.base/implicitptr.exp |   78 +++
 testsuite/systemtap.base/implicitptr.stp |   21 +
 4 files changed, 642 insertions(+), 298 deletions(-)
 create mode 100644 testsuite/systemtap.base/implicitptr.c
 create mode 100644 testsuite/systemtap.base/implicitptr.exp
 create mode 100644 testsuite/systemtap.base/implicitptr.stp


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


                 reply	other threads:[~2010-09-15 20:26 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=20100915202636.8440.qmail@sourceware.org \
    --to=roland@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).