From: Michael S. Zick <mszick@goquest.com>
To: "khalid aggag" <khalidaggag@hotmail.com>, gcc@gcc.gnu.org
Subject: Re: A FrontEnd in C++?
Date: Sat, 17 Aug 2002 18:06:00 -0000 [thread overview]
Message-ID: <02081720060000.04838@localhost.localdomain> (raw)
In-Reply-To: <F37crCgXAC98D6B8MK9000097e3@hotmail.com>
On Saturday 17 August 2002 05:45 pm, khalid aggag wrote:
> I am currently developing a new Frontend for an educational language for
> GCC. I have the language's lexical analysis and parsing modules in C++. Is
> it possible to develop a frontend for gcc written completely in C++? How
> would I make up for the different function naming and calling conventions
> between C and C++? Thanx alot in advance.
>
>
> Khalid Aggag
Aside from the technical questions...
Have you considered the bootstrapping issues?
Originally, GCC could be bootstrapped with "any 'ol" C compiler.
Now, it can be bootstrapped with (almost) "any 'ol C compiler PLUS an Ada
compiler that produces "link compatable" object files.
Writing a front end in C++ would make that process:
Stage0: any 'ol C compiler -> gcc<c, c++>
Stage1: gcc<c, c++> + new_frontend -> gcc<c, c++, New>
Stage2: gcc<c, c++, New> -> presumably_finished_compiler
Stage3: presumably_finished_compiler -> finished_compiler
Compare Stage2 with Stage3, if same; then done; else punt!
And just to make it more interesting - add bootstrapping Ada in the above
process at the same time.
Mike
next prev parent reply other threads:[~2002-08-17 18:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 15:45 khalid aggag
2002-08-17 18:06 ` Michael S. Zick [this message]
2002-08-19 0:46 ` Fergus Henderson
2002-08-19 1:02 ` Zack Weinberg
2002-08-19 2:18 ` Gabriel Dos Reis
2002-08-19 2:42 ` Michael S. Zick
2002-08-21 10:40 ` Zack Weinberg
2002-08-21 10:59 ` Michael Matz
2002-08-21 11:18 ` Zack Weinberg
2002-08-21 11:25 ` Daniel Berlin
2002-08-21 11:35 ` Michael Matz
2002-08-21 11:50 ` Daniel Berlin
2002-08-22 13:03 ` Pop Sébastian
2002-08-22 13:11 ` Diego Novillo
2002-08-22 13:19 ` Pop Sébastian
2002-08-22 20:19 ` Daniel Berlin
2002-08-22 12:47 ` Gabriel Dos Reis
2002-08-21 11:10 ` Phil Edwards
2002-08-21 11:43 ` Ross Smith
2002-08-21 12:24 ` Zack Weinberg
2002-08-22 12:47 ` Gabriel Dos Reis
2002-08-21 21:51 ` Fergus Henderson
2002-08-22 12:47 ` Gabriel Dos Reis
2002-08-22 14:16 ` Zack Weinberg
2002-08-22 15:41 ` Gabriel Dos Reis
2002-08-23 2:20 ` Fergus Henderson
2002-08-23 13:19 ` Toon Moene
2002-08-24 2:25 ` Kai Henningsen
2002-08-19 6:55 ` Alexandre Oliva
2002-08-19 8:50 ` Michael S. Zick
2002-08-19 7:20 ` Diego Novillo
2002-08-19 12:20 ` Mike Stump
2002-08-20 2:19 ` Florian Weimer
2002-08-19 10:51 ` Matt Austern
2002-08-20 11:18 ` Kelley Cook
2002-08-20 11:38 ` Kevin Handy
2002-08-18 14:36 khalid aggag
2002-08-18 15:37 ` Michael S. Zick
2002-08-18 22:48 ` Per Bothner
2002-08-19 16:18 Robert Dewar
2002-08-21 11:41 Robert Dewar
2002-08-21 12:59 ` Geoff Keating
2002-08-21 11:53 Robert Dewar
2002-08-21 12:03 ` Graham Stott
2002-08-21 16:16 ` Zack Weinberg
2002-08-21 11:54 Robert Dewar
2002-08-21 16:19 Richard Kenner
2002-08-22 14:17 ` Zack Weinberg
2002-08-21 16:26 Billinghurst, David (CRTS)
2002-08-21 17:19 Robert Dewar
2002-08-21 17:19 Robert Dewar
2002-08-21 18:00 Richard Kenner
2002-08-22 1:54 Robert Dewar
2002-08-22 13:50 Chris Lattner
2002-08-22 14:53 Robert Dewar
2002-08-22 20:37 ` Geoff Keating
2002-08-22 21:36 ` Hans-Peter Nilsson
2002-08-23 3:08 Robert Dewar
2002-08-24 6:54 Robert Dewar
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=02081720060000.04838@localhost.localdomain \
--to=mszick@goquest.com \
--cc=gcc@gcc.gnu.org \
--cc=khalidaggag@hotmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).