From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] My Eu paper, mark 2 From: Charles Forsyth In-Reply-To: <3ebe66e46b2d686c0b47607a294e5886@collyer.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Sat, 11 Oct 2003 10:21:52 +0100 Topicbox-Message-UUID: 6cd73052-eacc-11e9-9e20-41e7f4b1d025 >>yacc. Ken claims that it takes 3 weeks to port his compiler (and >>assembler and loader) to a new machine, but that's with Ken doing the >>porting, working long days. it can be somewhat less than that. it rather depends on the nature of the target processor, whether there's something similar in the existing suite, and whether you feel the need to do an interpreter as well. i've found it the easiest compiler suite to port that produces reasonable code. i like its broad division of work for the machine analysis. unlike the usual assembler/linker grunge, to which people seem glued, there isn't repetition of work as regards the instruction encoding. lcc is probably quicker to port but then you still need the usual assembler/loader grunge, and the code isn't as good. (nice compiler, though.) >>problems rather than any real need. I don't know how many people were >>used to implement the full Algol 68 language either. And MIPS's Algol68R and Algol68C were both done by comparatively small groups, although it would probably be fair to say that both compilers did subsets.