From: fche@redhat.com (Frank Ch. Eigler)
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: "David Smith" <dsmith@redhat.com>, <systemtap@sources.redhat.com>
Subject: Re: precompiled probing scenarios
Date: Thu, 26 Oct 2006 01:07:00 -0000 [thread overview]
Message-ID: <y0mr6wvubox.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <C56DB814FAA30B418C75310AC4BB279DD41D4A@scsmsx413.amr.corp.intel.com>
"Stone, Joshua I" <joshua.i.stone@intel.com> writes:
> [...]
> That's partly my point. Those pairings are functionally equivalent,
> right? So why should the code we generate show any differences?
> [...]
> My hope is that someday the translator will also treat less obvious
> cases like these as identical: [...]
While none of these is a bad idea, I see little practical necessity
for normalization. How many nearly-identical scripts do we ship? How
many normalizably-identical scripts do people actually use? If the
answer is "not many" or even "none", I wouldn't worry about it.
- FChE
next prev parent reply other threads:[~2006-10-26 1:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 18:54 Stone, Joshua I
2006-10-26 1:07 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 0:29 Stone, Joshua I
2006-10-24 15:16 ` David Smith
2006-10-20 20:51 Stone, Joshua I
2006-10-20 18:44 Stone, Joshua I
2006-10-20 19:26 ` David Smith
2006-10-20 19:32 ` Frank Ch. Eigler
2006-10-20 19:50 ` David Smith
2006-10-20 20:13 ` Frank Ch. Eigler
2006-10-23 20:36 ` David Smith
2006-10-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` David Smith
2006-10-06 19:08 Frank Ch. Eigler
2006-10-06 20:33 ` David Smith
2006-10-06 20:40 ` Frank Ch. Eigler
2006-10-19 19:49 ` David Smith
2006-10-19 21:53 ` Frank Ch. Eigler
2006-10-20 13:50 ` David Smith
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=y0mr6wvubox.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=dsmith@redhat.com \
--cc=joshua.i.stone@intel.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).