9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] My Eu paper, mark 2
Date: Sat, 11 Oct 2003 10:21:52 +0100	[thread overview]
Message-ID: <a215287a830f7af9ca48a779e2abd2dd@caldo.demon.co.uk> (raw)
In-Reply-To: <3ebe66e46b2d686c0b47607a294e5886@collyer.net>

>>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.



  reply	other threads:[~2003-10-11  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 12:00 Laura Creighton
2003-10-10 22:11 ` Geoff Collyer
2003-10-11  9:21   ` Charles Forsyth [this message]
2003-10-11  9:27     ` Geoff Collyer
2003-10-11 21:28       ` Lyndon Nerenberg
2003-10-10 22:12 ` Geoff Collyer
2003-10-13  8:58 ` Douglas A. Gwyn
2003-10-17  2:58 [9fans] a problem I don't understand on a reinstall Russ Cox
2003-10-17 11:41 ` [9fans] My Eu paper, mark 2 John DeGood

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=a215287a830f7af9ca48a779e2abd2dd@caldo.demon.co.uk \
    --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).