From: Matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re[2]: [9fans] Rant (was Re: Plan9 and Ada95?)
Date: Thu, 8 Nov 2001 12:58:07 +0000 [thread overview]
Message-ID: <86580537899.20011108125807@proweb.co.uk> (raw)
In-Reply-To: <20011108122852.B3F96199DD@mail.cse.psu.edu>
>> Has anyone compared the efficiency of the code produced by GCC and the
>> Plan 9 compiler?
bbc> I recently re-read Jim Gray's paper `The 5-minute Rule.' It's interesting
bbc> to note that when he wrote the paper (1985) a meg of memory was $5K and a MIP
bbc> was $50K. Now, by my calulations, a meg is about $0.50 and a mip is about
bbc> $0.30.
the 1997 version of that paper is here :
http://ftp.research.microsoft.com/pub/TR/TR-97-33.doc
and here
http://research.microsoft.com/~gray/5_min_rule_SIGMOD.doc
bbc> The economics of CS used to be:
bbc> 1) correctness of programs
bbc> 2) time efficiency
bbc> 3) space efficiency
bbc> Considering the changes in speed and memory, I assert that for all but
bbc> the most demanding case, only 1) is still a limited resource.
bbc> What do these economics say about optimizing compilers?
I'm no compiler expert but it is my assertion that the popularity of
scripted languages indicates that the running time of many many
programs is not significant. Such that 1) can probably save you more
time/money in the long run anyway.
If the world has got time for transparent menus and java applets then
it can suffer not unrolling every loop and using registers when
possible.
My first encounter with optimizing compilers was ms C (ver 3 I think)
It used to do the ultimate optimization and just silently drop your
code into the bit bucket anyway!
next prev parent reply other threads:[~2001-11-08 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 12:30 bwc
2001-11-08 12:58 ` Matt [this message]
2001-11-09 0:06 ` Noah Diewald
2001-11-09 9:51 ` Taj Khattra
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=86580537899.20011108125807@proweb.co.uk \
--to=matt@proweb.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).