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-0.9.8-136-g2203b03 Date: Thu, 09 Jul 2009 23:20:00 -0000 [thread overview] Message-ID: <20090709232041.22945.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 2203b03262e340b25fc26996cc2786c1c02041e3 (commit) via 66c7d4c1a4147bc05abd1e69f41ec9d59685c433 (commit) from c145b9cb053a1275865302d23fb3072143534fc8 (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 2203b03262e340b25fc26996cc2786c1c02041e3 Author: Josh Stone <jistone@redhat.com> Date: Thu Jul 9 12:46:57 2009 -0700 Remove the filename copy from token->location The location already has a pointer to a stapfile with the filename, so there's no need to keep an extra copy. commit 66c7d4c1a4147bc05abd1e69f41ec9d59685c433 Author: Josh Stone <jistone@redhat.com> Date: Thu Jul 9 12:43:00 2009 -0700 Optimize string usage in the lexer This speeds up the parsing stage >2x, mostly by minimizing string construction and comparison where char comparison will do. ----------------------------------------------------------------------- Summary of changes: coveragedb.h | 11 ++-- elaborate.cxx | 24 +++--- parse.cxx | 223 ++++++++++++++++++++++++++------------------------------- parse.h | 15 ++-- 4 files changed, 127 insertions(+), 146 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-07-09 23:20 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=20090709232041.22945.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).