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.2-83-gc4782e0 Date: Thu, 22 Apr 2010 22:37:00 -0000 [thread overview] Message-ID: <20100422223743.28891.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 c4782e01eebec8001fbdb3b2e94c55b3468a2f9e (commit) via 839325a1089805f9c309f2a61cb6f6e757c0faf0 (commit) via e76c6d65448d97cc530339cf903cc75cb293557f (commit) via 8e00730c33bb33484644b71546648e892306cccd (commit) via f6abaa092e44445645154dec3ca5960ff5ebeefb (commit) via 5abd364dc69dc27d49b664b35ad36c25fcf82fbe (commit) from eada04085180e48bfd376bbc703da8489ce535cc (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 c4782e01eebec8001fbdb3b2e94c55b3468a2f9e Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 18:53:03 2010 -0700 Consolidate load_aggregate logic * translate.cxx (c_unparser::load_aggregate): Every caller needed to figure out pre_agg and var vs. mapvar, so let's do it for them. (c_unparser::visit_foreach_loop): Defer more to load_aggregate. (c_unparser::visit_arrayindex): Ditto. (c_unparser::visit_print_format): Ditto. (c_unparser::visit_stat_op): Ditto. (c_tmpcounter::load_aggregate): New, determine all the tmps needed to mirror c_unparser::load_aggregate. (c_tmpcounter::visit_foreach_loop): Call load_aggregate. (c_tmpcounter::visit_arrayindex): Ditto. (c_tmpcounter::visit_print_format): Ditto. (c_tmpcounter::visit_stat_op): Ditto. commit 839325a1089805f9c309f2a61cb6f6e757c0faf0 Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 17:46:38 2010 -0700 Let hist buckets be printed with other arguments We already have quite a kludge to fall back from the print(@hist(...)) special case if the @hist happens to have a bucket arrayindex on it. In that case we're printing scalars, so we can allow the print to contain other scalar values too. As noted in a comment, this still fails if the arrayindex is the start of a larger expression. :( * parse.cxx (parser::parse_symbol): Parse other print args after @hist. * testsuite/buildok/print_histogram_entry.stp: Add a few prints to exercise this (and one that still doesn't work). commit e76c6d65448d97cc530339cf903cc75cb293557f Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 17:24:08 2010 -0700 PR2168: Support foreach over pmap histograms * translate.cxx (c_tmpcounter::visit_foreach_loop): Add tmps for hist indexes, only if it's not already cached from an outer foreach. (c_unparser::visit_foreach_loop): Allow the possibility that the hist var might need to be a mapvar. * testsuite/buildok/pmap_foreach.stp: Add a nested foreach loop. * testsuite/systemtap.base/foreach_value.stp: Add a nested foreach loop. * testsuite/systemtap.base/foreach_value.exp: Add expected output. commit 8e00730c33bb33484644b71546648e892306cccd Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 15:35:01 2010 -0700 PR2168: Support break/continue in histogram bucket foreach * translate.cxx (c_unparser::visit_foreach_loop): Output break and continue labels for histogram bucket foreach. * testsuite/buildok/iterate_histogram_buckets.stp: Enable test. commit f6abaa092e44445645154dec3ca5960ff5ebeefb Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 15:31:00 2010 -0700 Simplify c_unparser's break/continue a little commit 5abd364dc69dc27d49b664b35ad36c25fcf82fbe Author: Josh Stone <jistone@redhat.com> Date: Wed Apr 21 15:11:28 2010 -0700 Block local stats and arrays in pass 2 Parts of the translator get confused if stats or arrays are allowed through as locals. It's easier to block it in pass 2 as soon as we can detect this issue. * elaborate.cxx (typeresolution_info::check_local): Make sure that probe and function locals are scalar longs or strings. (semantic_pass_types): Call check_local for functions and probes. (symresolution_info::visit_symbol): Make auto-locals scalar. * testsuite/semko/local_array.stp: Test that local arrays are rejected. * testsuite/semko/local_stat.stp: Test that local stats are rejected. * testsuite/transko/array01.stp: Move to semko. ----------------------------------------------------------------------- Summary of changes: elaborate.cxx | 30 ++++ elaborate.h | 1 + parse.cxx | 12 ++ testsuite/buildok/iterate_histogram_buckets.stp | 6 +- testsuite/buildok/pmap_foreach.stp | 9 + testsuite/buildok/print_histogram_entry.stp | 7 +- testsuite/{transko => semko}/array01.stp | 2 +- testsuite/semko/local_array.stp | 8 + testsuite/semko/local_stat.stp | 8 + testsuite/systemtap.base/foreach_value.exp | 4 + testsuite/systemtap.base/foreach_value.stp | 7 + translate.cxx | 201 +++++++---------------- 12 files changed, 150 insertions(+), 145 deletions(-) rename testsuite/{transko => semko}/array01.stp (91%) create mode 100755 testsuite/semko/local_array.stp create mode 100755 testsuite/semko/local_stat.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-04-22 22:37 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=20100422223743.28891.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).