From: Ian Lance Taylor <iant@google.com>
To: Ivan Levashew <I.Levashew@bluebottle.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc-in-cxx branch created
Date: Thu, 26 Jun 2008 03:12:00 -0000 [thread overview]
Message-ID: <m38wwsvqir.fsf@google.com> (raw)
In-Reply-To: <g3s99g$oc0$1@ger.gmane.org> (Ivan Levashew's message of "Wed\, 25 Jun 2008 09\:19\:19 +0700")
Ivan Levashew <I.Levashew@bluebottle.com> writes:
>> Your comment makes little sense in context. Nobody could claim that
>> the existing gengtype code is simple. Not many people understand how
>> it works at all. In order to support STL containers holding GC
>> objects, it will need to be modified.
>
> I'm sure there is a library of GC-managed components in C++.
I'm sure there is too. In gcc we use the same data structures to
support both GC and PCH. Switching to a set of C++ objects is likely
to be a complex and ultimately unrewarding task.
>> I don't know what you mean by your reference to the Cyclone variant of
>> C, unless you are trying to say something about gcc's use of garbage
>> collection.
>>
>
> Cyclone has many options for memory management. I don't know for sure
> if there is a need for GC in GCC at all.
I would prefer it if gcc didn't use GC, but it does, and undoing that
decision will be a long hard task which may never get done.
> Cyclone has a roots not only in C, but also ML. Some techniques like
> pattern matching, aggregates, variadic arrays, tuples looks to be more
> appropriate here than their C++'s metaprogrammed template analogues.
I guess I don't know Cyclone. If you are suggesting that we use
Cyclone instead of C++, I think that is a non-starter. We need to use
a well-known widely-supported language, and it must be a language
which gcc itself supports.
Ian
next prev parent reply other threads:[~2008-06-26 3:12 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 6:02 Ian Lance Taylor
2008-06-18 13:18 ` Doug Gregor
2008-06-19 6:07 ` Kaveh R. GHAZI
2008-06-19 6:55 ` Kaveh R. GHAZI
2008-06-19 7:42 ` Gabriel Dos Reis
2008-06-19 8:10 ` Kaveh R. GHAZI
2008-06-19 8:40 ` Gabriel Dos Reis
2008-06-19 12:23 ` Ian Lance Taylor
2008-06-19 17:30 ` Kaveh R. GHAZI
2008-06-19 17:42 ` Ian Lance Taylor
2008-06-19 20:28 ` Kaveh R. GHAZI
2008-06-20 1:14 ` Aaron Gray
2008-06-20 4:15 ` Kaveh R. GHAZI
2008-06-24 14:31 ` Tom Tromey
2008-06-18 15:42 ` Diego Novillo
2008-06-18 15:57 ` Ian Lance Taylor
2008-06-18 17:00 ` Thomas Neumann
2008-06-18 17:19 ` Joseph S. Myers
2008-06-19 10:47 ` Gabriel Dos Reis
2008-06-19 12:25 ` Ian Lance Taylor
2008-06-19 13:01 ` Gabriel Dos Reis
2008-06-19 13:14 ` Joseph S. Myers
2008-06-19 14:42 ` Ian Lance Taylor
2008-06-19 15:47 ` Jens-Michael Hoffmann
2008-06-19 16:21 ` Ian Lance Taylor
2008-06-19 16:32 ` Jens-Michael Hoffmann
2008-06-19 17:27 ` Ian Lance Taylor
2008-06-19 18:04 ` Daniel Berlin
2008-06-19 18:24 ` Paweł Sikora
2008-06-19 19:36 ` Ian Lance Taylor
2008-06-21 12:15 ` Ivan Levashew
2008-06-21 20:41 ` Ian Lance Taylor
2008-06-25 2:08 ` Ivan Levashew
2008-06-26 3:12 ` Ian Lance Taylor [this message]
2008-07-02 19:32 ` Hendrik Boom
2008-07-03 9:18 ` Daniel Berlin
2008-07-03 15:57 ` Hendrik Boom
2008-06-24 1:54 ` Tom Tromey
2008-06-24 9:34 ` Richard Guenther
2008-06-21 9:50 ` Ivan Levashew
2008-06-22 23:30 Bruno Haible
2008-06-23 5:12 ` Chris Lattner
2008-06-23 6:58 ` Arnaud Charlet
2008-06-23 10:39 ` Joseph S. Myers
2008-06-23 10:49 ` Arnaud Charlet
2008-06-23 11:14 ` Bruno Haible
2008-06-24 9:30 ` Gabriel Dos Reis
2008-06-24 10:47 ` Bruno Haible
2008-06-24 11:21 ` Gabriel Dos Reis
2008-06-23 11:01 ` Ian Lance Taylor
2008-06-24 11:20 ` Bruno Haible
2008-06-24 11:23 ` Gabriel Dos Reis
2008-06-24 17:51 ` Ian Lance Taylor
2008-06-25 5:49 ` Ross Smith
2008-06-24 9:23 ` 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=m38wwsvqir.fsf@google.com \
--to=iant@google.com \
--cc=I.Levashew@bluebottle.com \
--cc=gcc@gcc.gnu.org \
/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).