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.0-119-g81fb86d
Date: Tue, 20 Oct 2009 01:37:00 -0000	[thread overview]
Message-ID: <20091020013718.32024.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  81fb86d83da9964e7d9e2330d78b2008f18054e4 (commit)
      from  892e5de27d2f275e2d7c2160d81fe9e0c87b1ee1 (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 81fb86d83da9964e7d9e2330d78b2008f18054e4
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Oct 19 18:11:58 2009 -0700

    Improve some runtime struct layouts
    
    Guided by pahole, I've shaved off a few padding bytes here and there.
    New sizes on x86_64:
    
      stap_task_finder_target  192 -> 184
      stap_itrace_probe        216 -> 208
      stap_utrace_probe        328 -> 312
      stap_uprobe_tf           200 -> 192
      stap_uprobe_spec          48 ->  40
    
    I only changed field layouts, not types or names, so this should be
    perfectly safe. (FLW)

-----------------------------------------------------------------------

Summary of changes:
 runtime/task_finder.c |    4 ++--
 tapset-utrace.cxx     |    2 +-
 tapsets.cxx           |    2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-10-20  1: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=20091020013718.32024.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: link
Be 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).