From: Daniel Berlin <dberlin@dberlin.org>
To: Pop Sébastian <pop@gauvain.u-strasbg.fr>
Cc: Michael Matz <matz@suse.de>,
Zack Weinberg <zack@codesourcery.com>, <gcc@gcc.gnu.org>
Subject: Re: A FrontEnd in C++?
Date: Thu, 22 Aug 2002 20:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0208222316550.4066-100000@dberlin.org> (raw)
In-Reply-To: <20020822200333.GA12732@gauvain.u-strasbg.fr>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, 22 Aug 2002, [iso-8859-1] Pop Sébastian wrote:
> Hi,
>
> On Wed, Aug 21, 2002 at 02:50:47PM -0400, Daniel Berlin wrote:
> > >
> > > P.S.: I even thought sometimes about (re)writing some of the optimizations
> > > in C++.
> >
> > I've actually started doing it many times.
> > In particular, i've still got the start of an interprocedural middle-end
> > (IE takes trees from many modules) written in C++.
> >
> > You can't believe how nice it is to just simply be able to do things like
> > std::set<tree>, etc.
> > It seems trivial, but it's really a lot nicer to work with classes.
> >
>
> Why not beginning to write the AST optimizer in C++?
I was under the impression it would be rejected (IE never be accepted in
the maniline), so i never took it further.
>
> The AST optimizer is not needed for building the C, nor the C++ compiler,
> but once g++ is built we could build the AST optimizer.
Sure, I knew this, but I still felt it wouldn't be accepted because of the
associated stigma writing non-C seems to have in the GCC development
world.
:)
next prev parent reply other threads:[~2002-08-22 20:19 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
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 [this message]
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=Pine.LNX.4.44.0208222316550.4066-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
--cc=pop@gauvain.u-strasbg.fr \
--cc=zack@codesourcery.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).