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.1-253-g9fab226 Date: Thu, 18 Mar 2010 22:51:00 -0000 [thread overview] Message-ID: <20100318225102.5864.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 9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3 (commit) from 8fb91f5fe6cdcab379144f4ebddae6f72816f2c3 (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 9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3 Author: Josh Stone <jistone@redhat.com> Date: Thu Mar 18 15:39:42 2010 -0700 PR11346: Move the skip-badvars logic into const-folding The const_folder is where we prune constant expressions, like conditionals based on a @defined($foo), so we want to give this a chance to work before skip-badvars comes in and throws a warning. As an added bonus, this makes skip-badvars more generic, so it will work even for non-dwarf $target variables. * elaborate.cxx (const_folder::visit_target_symbol): Enact skip-badvars. * tapsets.cxx (dwarf_var_expanding_visitor::visit_target_symbol): Don't worry about badvars here anymore. Save the error now, clean up later. * testsuite/semok/badvar_undefined.stp: Test that @defined with skip-badvars doesn't throw any warnings. ----------------------------------------------------------------------- Summary of changes: elaborate.cxx | 24 ++++++++++++++++++++ tapsets.cxx | 39 +++++++++------------------------ testsuite/semok/badvar_undefined.stp | 7 ++++++ 3 files changed, 42 insertions(+), 28 deletions(-) create mode 100755 testsuite/semok/badvar_undefined.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-03-18 22:51 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=20100318225102.5864.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: linkBe 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).