This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch checked in for K&R stage1 cc on obtabs.c
- To: N8TM at aol dot com, craig at jcb-sc dot com
- Subject: Re: Patch checked in for K&R stage1 cc on obtabs.c
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Wed, 26 May 1999 09:37:30 -0400 (EDT)
- Cc: egcs-patches at egcs dot cygnus dot com, law at cygnus dot com, oliva at dcc dot unicamp dot br
> From: craig@jcb-sc.com
>
> The last part might be right, but I don't know of any reason why I can't
> fairly easily ensure that g77 will build on K&R C compilers as part of
> the rewrite.
>
> As I said, the back end already provides most, if not all, of the important
> facilities.
>
> I believe it's the case that, right now, to "fix" g77's K&R bugs, all
> that is needed is to PROTO-ize a whole bunch of definitions and
> declarations (presumably a Perl or Guile script could do that right quick)
> *and* -- the harder, and less-worthwhile part -- move all the
> statement-expressions in target.h into target.c as proper functions.
>
> tq vm, (burley)
Besides the stuff you mentioned above, you also will need to
handle any uses of the # or ## operators. Perhaps something more.
But you're right, it wouldn't be insurmountable.
IMHO, the issue isn't whether you *can* do it. The question I
have is *why* would you do it? IIRC, K&R support is only so people
can bootstrap the C compiler. Don't we want to encourage people to
compile g77 with gcc (preferably the gcc they just bootstrapped?)
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions