From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c vs. gcc shootout
Date: Mon, 25 Feb 2002 18:13:06 +0000 [thread overview]
Message-ID: <20020225182129.2F99D19A3E@mail.cse.psu.edu> (raw)
>>It would be *even better* if the Plan 9 kernel were being compiled
>>with an optimizing compiler.
it didn't make any appreciable difference when that was tried years ago (not by us)
with Inferno, compiled with gcc on various platforms.
it didn't make any appreciable difference with my own O/S on the sun3 and i386,
and i suspect that's because in all those cases there was little code on
which heavy-duty optimisation makes much difference. there is a fair amount
of function calling but relatively little crunching. the main crunching that's
done is data movement or graphics and both are optimised separately using
non-compiler-specific techniques.
next reply other threads:[~2002-02-25 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 18:13 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 15:35 anothy
2002-02-25 17:11 ` Thomas Bushnell, BSG
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=20020225182129.2F99D19A3E@mail.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).