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.7-171-g600551c Date: Thu, 19 Apr 2012 21:22:00 -0000 [thread overview] Message-ID: <20120419212206.10522.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 600551ca9fb694d2757d66a4bf281dcf6934d9bf (commit) from 40c93fa13087b76e8caa28ad38fb2c6b4628c2c4 (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 600551ca9fb694d2757d66a4bf281dcf6934d9bf Author: Josh Stone <jistone@redhat.com> Date: Thu Apr 19 14:11:00 2012 -0700 PR13998: pretty-print bit fields numerically When a struct member has bit attributes, we should always pretty-print it as a number, even if the underlying type is a character. Since these attributes only show up in DWARF on the member, not the type die, we need to treat it as a special case from the struct member iteration. * tapsets.cxx (dwarf_pretty_print::recurse_bitfield): Print the incoming type numerically, regardless of whether it's a char. (dwarf_pretty_print::recurse_struct_members): If a member has a bit_offset attribute, use recurse_bitfield instead of normal recurse. * testsuite/systemtap.printf/pretty-bits.*: Test how bitfields are pretty-printed, both for ints and chars underneath. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 58 +++++++++++++++++++++++++++- testsuite/systemtap.printf/pretty-bits.exp | 9 ++++ testsuite/systemtap.printf/pretty-bits.h | 6 +++ testsuite/systemtap.printf/pretty-bits.stp | 21 ++++++++++ 4 files changed, 93 insertions(+), 1 deletions(-) create mode 100644 testsuite/systemtap.printf/pretty-bits.exp create mode 100644 testsuite/systemtap.printf/pretty-bits.h create mode 100644 testsuite/systemtap.printf/pretty-bits.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-04-19 21:22 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=20120419212206.10522.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).