From: Martin Hunt <hunt@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: 2.6 kernel syscall changes
Date: Mon, 09 Jan 2006 18:58:00 -0000 [thread overview]
Message-ID: <1136833139.3855.21.camel@monkey2> (raw)
In-Reply-To: <y0mvewtxork.fsf@toenail.toronto.redhat.com>
On Mon, 2006-01-09 at 13:03 -0500, Frank Ch. Eigler wrote:
> But the parameter access problem is real. It would be nice to have
> some solution that would be useful even with correct debuginfo.
>
> How about this: the translator could perform an early-stage
> optimization during pass 2, which removes some classes of
> subexpressions that have no side-effects. This would include
> assignments to variables that are never read. Probe aliases that copy
> a slew of $target variables into local script variables would quietly
> tolerate the unresolvability of just those variables that are not used
> by the end-user scripts.
If you could do that, it sounds like a nearly ideal solution.
You fix that, I'll try to fix the syscall tapset by putting it back in
one file and adding a bunch of conditionals on arch and kernel and we'll
see what things look like then. OK?
Martin
prev parent reply other threads:[~2006-01-09 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 21:40 Martin Hunt
2006-01-09 18:03 ` Frank Ch. Eigler
2006-01-09 18:58 ` Martin Hunt [this message]
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=1136833139.3855.21.camel@monkey2 \
--to=hunt@redhat.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
/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).