public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.8-6-g5e3d7f3
Date: Mon, 15 Jun 2009 11:43:00 -0000	[thread overview]
Message-ID: <20090615114318.1986.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  5e3d7f3a3aa8d11b67e74de0c3d9187c323cbff2 (commit)
      from  f07c3b680a722e27ed55bb5c9719fa5827ebfc75 (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 5e3d7f3a3aa8d11b67e74de0c3d9187c323cbff2
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Jun 15 13:37:39 2009 +0200

    PR10274 Fix exelib -O3 testcase.
    
    The testcase now uses noinline, an empty asm statement and a volatile
    variable to prevent the function getting inlined, being totally unrolled
    or the recursive call being replaced with an inner-iteration.
    
    This does defeat part of the testcase though, which was testing unwinding
    through an optimized recursive function. But it seems the best we can do.
    
    * testsuite/systemtap.exelib/exelib.exp: Add -O3 to the mix.
    * testsuite/systemtap.exelib/uprobes_exe.c: Use volatile bar and mark
      main_func noinline.
    * testsuite/systemtap.exelib/uprobes_lib.c: Use volatile foo and mark
      lib_func noinline.

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

Summary of changes:
 testsuite/systemtap.exelib/exelib.exp    |    3 +--
 testsuite/systemtap.exelib/uprobes_exe.c |   17 +++++++++++++----
 testsuite/systemtap.exelib/uprobes_lib.c |   17 +++++++++++++----
 3 files changed, 27 insertions(+), 10 deletions(-)


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


                 reply	other threads:[~2009-06-15 11:43 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=20090615114318.1986.qmail@sourceware.org \
    --to=mark@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).