From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] prof
Date: Fri, 11 Aug 2000 22:14:56 +0100 [thread overview]
Message-ID: <200008112116.RAA25987@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 90 bytes --]
the linker knows all.
i'll try to unearth the code, or reproduce it.
it wasn't hard.
[-- Attachment #2: Type: message/rfc822, Size: 2245 bytes --]
From: "D. Brownlee" <ancipites@earthlink.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] prof
Date: Fri, 11 Aug 2000 11:22:17 -0700
Message-ID: <39944459.C86EAAFE@earthlink.net>
It would be nice to see the linker
change. I was thinking of modifying
the compiler's 'codgen' to create a
bunch of temp files that identify
function definitions and the functions
called within them, then process those
to get a static flow graph.
forsyth@vitanuova.com wrote:
>
> >>Another question: has anyone done anything with the
> >>compiler to generate a static flow graph -- something
> >>like 'cflow'?
>
> i have changes to one of the linkers somewhere.
> it also checked stack depth.
next reply other threads:[~2000-08-11 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 21:14 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-11 14:23 Russ Cox
2000-08-11 14:19 forsyth
2000-08-11 18:22 ` D. Brownlee
2000-08-15 4:15 ` D. Brownlee
2000-08-11 13:10 D. Brownlee
2000-08-11 14:03 ` D. Brownlee
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=200008112116.RAA25987@cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).