From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam hacking - a couple of fixes that may apply t
Date: Fri, 4 Jul 2003 08:59:53 +0000 [thread overview]
Message-ID: <3F051817.3050207@null.net> (raw)
In-Reply-To: <002701c341ce$35f939e0$d2944251@insultant.net>
boyd, rounin wrote:
> rob wrote in one of the sam papers (iirc) that most people don't use
> complex sam commands. i used to be like that, until i learnt the error
> of my ways, so now i construct fairly complex stuff and refine it till
> it's right.
In BRL's MUVES project, one of our Makefile targets was a
profiled source listing, i.e. execution counts (for a test
run) alongside each source line. Since there was no tool
on our Unix systems that did that, I cobbled one up as a
combination of existing tools and a "sam" script that was
several hundred characters long. Worked fine!
I have a file of "macors" for sam; I open that file as one
file within "sam", then snarf and send to execute when
needed.
next prev parent reply other threads:[~2003-07-04 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 18:30 Richard C Bilson
2003-07-04 1:47 ` boyd, rounin
2003-07-04 8:59 ` Douglas A. Gwyn [this message]
2003-07-04 10:08 ` boyd, rounin
2003-07-04 15:36 ` Derek Fawcus
2003-07-07 8:33 ` Douglas A. Gwyn
[not found] <2149465875@snellwilcox.com>
2003-07-03 17:06 ` steve.simon
2003-07-03 17:41 ` Derek Fawcus
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=3F051817.3050207@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).