From: Matt Austern <austern@apple.com>
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: Ziemowit Laski <zlaski@apple.com>,
gcc-patches@gcc.gnu.org, "Joseph S. Myers" <jsm@polyomino.org.uk>
Subject: Unified front end for C and C++ (was Re: New C parser [patch])
Date: Tue, 26 Oct 2004 00:03:00 -0000 [thread overview]
Message-ID: <2A6B2DDE-26E1-11D9-A96B-000A95AA5E5E@apple.com> (raw)
In-Reply-To: <417D8F67.5070105@coyotegulch.com>
On Oct 25, 2004, at 4:42 PM, Scott Robert Ladd wrote:
> Ziemowit Laski wrote:
>> While I don't buy these time estimates (not both simultaneously,
>> anyway), I do
>> agree that you would take a performance hit, at least in the
>> short-term,
>> especially for plain C code.
>
> I don't think this is a hit GCC's users can afford at this point.
> Another compile time regression may bring the hordes with pitchforks
> and torches... ;)
>
> Also, C and C++ are heading down different and incompatible paths. It
> will be increasingly difficult to manage the subtle-but-important
> differences in a single front end if the two languages continue to
> diverge.
On the one hand, that sounds plausible. On the other hand: gcc is the
only compiler I know of that has separate source bases for the C and
C++ front ends. Certainly EDG, MetroWerks, and Microsoft use the same
source base for both, and at least one of those three uses not only the
same source base but the same executable.
It may very well be true that getting from where we are to a common
front end for C and C++ would be so hard that it's not worth doing.
But we do have an existence proof that such a compiler is possible and
that it's can be maintainable and fast.
(Changing the subject line because this no longer has much to do with
Joseph's patch.)
--Matt
next prev parent reply other threads:[~2004-10-25 23:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:25 New C parser [patch] Joseph S. Myers
2004-10-23 2:39 ` Steven Bosscher
2004-10-23 4:15 ` Joseph S. Myers
2004-10-23 5:44 ` Scott Robert Ladd
2004-10-24 22:49 ` Joseph S. Myers
2004-10-26 0:32 ` Zack Weinberg
2004-10-26 1:03 ` Andrew Pinski
2004-10-26 1:03 ` Zack Weinberg
2004-10-26 1:11 ` Joseph S. Myers
2004-10-26 8:23 ` Zack Weinberg
2004-10-26 1:30 ` Gabriel Dos Reis
2004-10-26 1:06 ` Joseph S. Myers
2004-10-26 2:47 ` Joseph S. Myers
2004-10-26 3:48 ` Mark Mitchell
2004-10-26 12:21 ` Kyuupi
2004-10-26 12:32 ` Joseph S. Myers
2004-10-26 11:42 ` Joseph S. Myers
2004-10-27 19:04 ` Richard Henderson
2004-10-27 19:11 ` Richard Guenther
2004-10-27 19:41 ` Zack Weinberg
2004-10-27 19:31 ` Zack Weinberg
2004-10-27 21:31 ` Richard Henderson
2004-10-28 7:38 ` Alan Modra
2004-10-27 20:25 ` Joseph S. Myers
2004-10-25 22:33 ` Ziemowit Laski
2004-10-25 22:51 ` Joseph S. Myers
2004-10-25 23:45 ` Ziemowit Laski
2004-10-25 23:53 ` Scott Robert Ladd
2004-10-26 0:03 ` Matt Austern [this message]
2004-10-26 1:26 ` Unified front end for C and C++ (was Re: New C parser [patch]) Scott Robert Ladd
2004-10-26 1:43 ` Gabriel Dos Reis
2004-10-26 2:01 ` Scott Robert Ladd
2004-10-26 15:38 ` Gabriel Dos Reis
2004-10-26 0:28 ` New C parser [patch] Ziemowit Laski
2004-10-26 1:20 ` Scott Robert Ladd
2004-10-26 6:08 ` Unified C and C++ front end (was Re: New C parser [patch]) Matt Austern
2004-10-26 11:14 ` Joseph S. Myers
2004-10-26 16:04 ` Gabriel Dos Reis
2004-10-26 16:51 ` Joseph S. Myers
2004-10-26 0:37 ` New C parser [patch] Joseph S. Myers
2004-10-26 0:03 ` Stan Shebs
2004-10-26 1:46 ` Gabriel Dos Reis
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=2A6B2DDE-26E1-11D9-A96B-000A95AA5E5E@apple.com \
--to=austern@apple.com \
--cc=coyote@coyotegulch.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
--cc=zlaski@apple.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).