Re: GNU cc for HCX-9 and other GNU compiler stuff (M2)

gnu@toad.com
Sat, 01 Oct 88 18:34:14 -0700

          From comp.compilers

Related articles
Re: GNU cc for HCX-9 and other GNU compiler stuff (M2) gnu@toad.com (1988-10-01)
Re: GNU cc for HCX-9 and other GNU compiler stuff (M2) tower@bu-it.bu.edu (Leonard H. Tower Jr.) (1988-10-02)
Re: GNU cc for HCX-9 and other GNU compiler stuff (M2) harvard!cs.buffalo.edu!bowen (1988-10-13)
| List of all articles for this month |

In-Reply-To: <2725@ima.ima.isc.com>
Date: Sat, 01 Oct 88 18:34:14 -0700
From: gnu@toad.com

There is a group (I think in Buffalo, NY) porting gcc to the Tahoe.
Keith Bostic (bostic@okeeffe.berkeley.edu) is in touch with this work
and could tell you more.


Gcc is intended to have different front end parsers. It is currently
being used to compile both c and c++, using separate front ends.
Some further work remains to make it possible to build either a gcc
or a g++ (c++ compiler) in the same source directory, but the compiler
is definitely moving in this direction.


If I was to write a "gmm" (GNU Modula-2), I'd build an M2 parser in
place of the existing "c-parse.y" module, make whatever changes
throughout the rest of the code I needed (e.g. new types of scopes or
symbol table info; new operators; etc), and get it running reliably.
By then, if RMS has rearranged C and C++ to be buildable from the same
directory, I'd restructure my sources into his format and send 'em in
to him; otherwise would send in my language-independent changes (e.g.
back end changes) for merging, and track his releases for a few months
until the restructuring is done. (That seems to be what g++ is doing.)


John Gilmore
[From gnu@toad.com]
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.