From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] request for more GSoC project suggestions
Date: Wed, 25 Mar 2009 19:02:41 -0700 [thread overview]
Message-ID: <2C13A7A6-8BEF-44E3-9D61-B8E30DF9CD3D@sun.com> (raw)
In-Reply-To: <20090326010928.STYN13097.fed1rmmtao102.cox.net@fed1rmimpo01.cox.net>
On Mar 25, 2009, at 6:10 PM, Chris Brannon wrote:
> Erik Quanstrom wrote:
>> On Wed Mar 25 16:39:16 EDT 2009, cmbrannon@cox.net wrote:
>>> The Comeau C++ compiler [1] uses the cfront technique, doesn't
>>> it? It is
>>> supposed to be very standards-compliant.
>>>
>>> [1] http://www.comeaucomputing.com
>>
>> where do they claim this? i see a claim that they
>> accept cfront-isms, but that's a different claim.
>
> Quoting http://comeaucomputing.com/faqs/genfaq.html#ccompiler
>
> "Input C++ code is translated into internal compiler trees and
> symbol tables
> looking nothing like C++ or C. As well,
> it generates an internal proprietary intermediate form.
> But instead of using a proprietary back end code generator,
> Comeau C++ 4.3.3 generates C code as its output."
>
> Isn't that what cfront did, more or less?
Not really, no. In their case, I believe, C language is treated
as an intermediate language. It has no traces of the Cisms
of the original C++ code. It is as mangled as an assembler
would be if you do g++ -S foo.cc.
cfront (well, at least the original one) still preserved most
of the original code (as do most of thing like cyclone, cilk, etc.).
Thanks,
Roman.
next prev parent reply other threads:[~2009-03-26 2:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:16 Charles Forsyth
2009-03-25 15:06 ` Devon H. O'Dell
2009-03-26 5:19 ` lucio
2009-03-26 13:18 ` Devon H. O'Dell
2009-03-26 15:03 ` lucio
2009-03-26 15:17 ` lucio
2009-03-25 19:57 ` Paul Lalonde
2009-03-25 20:12 ` Devon H. O'Dell
2009-03-25 20:19 ` erik quanstrom
2009-03-25 20:28 ` Devon H. O'Dell
2009-03-25 20:38 ` Chris Brannon
2009-03-26 0:47 ` erik quanstrom
2009-03-26 1:10 ` Chris Brannon
2009-03-26 2:02 ` Roman Shaposhnik [this message]
2009-03-25 20:39 ` Paul Lalonde
2009-03-25 21:12 ` Charles Forsyth
2009-03-26 1:11 ` Roman V. Shaposhnik
2009-03-26 1:51 ` Paul Lalonde
2009-03-26 2:01 ` Roman Shaposhnik
2009-03-26 2:01 ` Devon H. O'Dell
2009-03-25 20:40 ` James Tomaschke
2009-03-25 22:48 ` Paul Lalonde
2009-03-25 23:20 ` Devon H. O'Dell
2009-03-25 23:26 ` erik quanstrom
2009-03-26 2:03 ` Devon H. O'Dell
2009-03-26 4:43 ` erik quanstrom
2009-03-26 2:05 ` Roman Shaposhnik
2009-03-26 14:21 ` Joel C. Salomon
2009-03-26 15:09 ` Juan M. Mendez
2009-03-26 15:18 ` Devon H. O'Dell
2009-03-26 16:23 ` [9fans] LLVM & Exceptions (Was re. request for more GSoC project suggestions) Joel C. Salomon
2009-03-26 0:09 ` [9fans] request for more GSoC project suggestions Federico G. Benavento
2009-03-26 1:54 ` Devon H. O'Dell
2009-03-26 10:41 ` Charles Forsyth
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=2C13A7A6-8BEF-44E3-9D61-B8E30DF9CD3D@sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).