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.3-310-gf13fc0d Date: Fri, 19 Nov 2010 22:13:00 -0000 [thread overview] Message-ID: <20101119221343.12666.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 f13fc0dbee710736a011a0f22e0a125e687ba6cd (commit) from 51d141e0aed241d741d256d483fc86f2d830ba9c (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 f13fc0dbee710736a011a0f22e0a125e687ba6cd Author: Josh Stone <jistone@redhat.com> Date: Fri Nov 19 14:00:38 2010 -0800 Make lex_cast work numerically with [u]int8_t These were getting treated by istream like char types, which would always fail our generic template since eof isn't reached. There's not much point to using lex_cast<char> anyway, since str[0] will do the same, so I've specialized lex_cast with [u]int8_t to read numerically. The only place we use this so far is in SDT V3 parsing constants. SDT doesn't yet emit 1-byte arguments, but it may in the future. * util.h (lex_cast<int8_t>): Read via int16_t to stay numeric. (lex_cast<uint8_t>): Same, with uint16_t. ----------------------------------------------------------------------- Summary of changes: util.h | 22 ++++++++++++++++++++++ 1 files changed, 22 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-19 22:13 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=20101119221343.12666.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).