Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!spdcc!ima!compilers-sender
From: gnu@toad.com
Newsgroups: comp.compilers
Subject: Re: GNU cc for HCX-9 and other GNU compiler stuff (M2)
Message-ID: <2728@ima.ima.isc.com>
Date: 2 Oct 88 01:34:14 GMT
Sender: compilers-sender@ima.ima.isc.com
Reply-To: gnu@toad.com
Lines: 27
Approved: compilers@ima.UUCP
In-Reply-To: <2725@ima.ima.isc.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]
--
Send compilers articles to ima!compilers or, in a pinch, to Levine@YALE.EDU
Plausible paths are { decvax | harvard | yale | bbn}!ima
Please send responses to the originator of the message -- I cannot forward
mail accidentally sent back to compilers.  Meta-mail to ima!compilers-request