Related articles |
---|
Re: Thompson's Plan 9 C compiler peter@ficc.ferranti.com (1991-08-12) |
Re: Thompson's Plan 9 C compiler svensson@imec.imec.be (1991-08-13) |
Re: Thompson's Plan 9 C compiler davidsen@crdos1.crd.ge.com (1991-08-13) |
Re: Thompson's Plan 9 C compiler pardo@cs.washington.edu (1991-08-13) |
Re: Thompson's Plan 9 C compiler howard@research.att.com (1991-08-14) |
Re: Thompson's Plan 9 C compiler kurt@tc.fluke.COM (1991-08-15) |
Re: Thompson's Plan 9 C compiler oz@ursa.ccs.yorku.ca (1991-08-16) |
Re: Thompson's Plan 9 C compiler p4tustin!point4.com!carl@uunet.uu.net (1991-08-20) |
Newsgroups: | comp.compilers |
From: | howard@research.att.com |
Summary: | "non-portable" back-ends |
Keywords: | C, design |
Organization: | Compilers Central |
References: | 91-08-048 91-08-049 |
Date: | Wed, 14 Aug 91 09:39:12 EDT |
In article 91-08-049, svensson@imec.imec.be (Lars Svensson) writes:
>
> Note that the code generator proper is hand-written for each of these
> architectures. To quote the paper: "There is a considerable amount of
> talk in literature about automating this part of the compiler with a
> hardware description. Since this code generator is so small (less than
> 500 lines of C) and easy, it hardly seems worth the effort." ...
It really is true that Thompson's back end is easy to do for
another machine. We recently ported Plan 9 to the Safari,
the AT&T 386-based laptop, and it only took Ken a week or two
to get the compiler done. I spent about as long fiddling
with bitblt...
Howard Trickey
AT&T Bell Labs, Murray Hill
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.