From: paurea@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: [9fans] splitting the compiler
Date: Wed, 27 Feb 2002 16:32:00 +0100 [thread overview]
Message-ID: <15484.64496.974395.322869@nanonic.hilbert.space> (raw)
As I see it we have three sets of constraints here:
1) - being fast compiling
2) - generating fast code (even if it breaks...? )
3) - being portable
We can make the first and the second not exclusive by having -O flags so
while developing (you want fast compiling and no new bugs generated by the compiler) you don't use 2. The issue here is the 3rd constraint. If you add
a complex optimizer the code is less portable.
I think the only way out of that is having two independant compilers
(the may share a lot of codebase) say, 8c and 8co (optimized). The
idea is that 8c compiles 8co, 8c is portable, fast and simple.
8co is slow but generates fast code.
Not that I am writing any compiler, it is just a suggestion. :-)
By the way, I have just recompiled XFree86 tree and it has taken me
three quarters of an hour. That is not the path to follow!!!.
--
Saludos,
Gorka
"Curiosity sKilled the cat"
next reply other threads:[~2002-02-27 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 15:32 paurea [this message]
2002-02-28 10:13 ` Thomas Bushnell, BSG
2002-02-28 16:02 ` ozan s yigit
2002-02-28 16:53 ` Thomas Bushnell, BSG
2002-03-04 10:03 ` ozan s. yigit
2002-03-04 17:04 ` Thomas Bushnell, BSG
2002-02-28 9:04 forsyth
2002-02-28 9:42 ` Matt H
2002-02-28 17:21 forsyth
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=15484.64496.974395.322869@nanonic.hilbert.space \
--to=paurea@gsyc.escet.urjc.es \
--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).