public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <dosreis@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>,
	Richard Guenther <richard.guenther@gmail.com>,
	Matt <matt@use.net>,
	 	gcc@gcc.gnu.org
Subject: Re: Phase 1 of gcc-in-cxx now complete
Date: Mon, 29 Jun 2009 16:26:00 -0000	[thread overview]
Message-ID: <206fcf960906290723r45f2db6fkaf44cf89e432e2bc@mail.gmail.com> (raw)
In-Reply-To: <b609cb3b0906290339od04816ap9ba6ac49e84e2cf1@mail.gmail.com>

On Mon, Jun 29, 2009 at 5:39 AM, NightStrike<nightstrike@gmail.com> wrote:
> On Sat, Jun 27, 2009 at 6:25 PM, Ian Lance Taylor<iant@google.com> wrote:
>> Richard Guenther <richard.guenther@gmail.com> writes:
>>
>>> All that above said - do you expect us to carry both vec.h (for VEC in
>>> GC memory) and std::vector (for VECs in heap memory) (and vec.h
>>> for the alloca trick ...)?  Or do you think we should try to make the GTY
>>> machinery C++ aware and annotate the standard library (ick...)?
>>
>> I expect us to write a GC allocator, and use that with std::vector.
>> This will require more hooks into the GC code, but I think it is doable.
>
> I'm curious about this.  I thought c++ wasn't a garbage collected
> language on purpose.

Many people are confused about what the 'purpose' is.

>  Why does GCC have one?  What purpose does it
> serve?  I'm not suggesting otherwise, but just trying to learn more
> about the way things are done.
>

This is usually an ingredient for long, heated, debates :-)

-- Gaby

  parent reply	other threads:[~2009-06-29 14:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27  0:26 Matt
2009-06-27  9:48 ` Ian Lance Taylor
2009-06-27 10:35   ` Richard Guenther
2009-06-27 13:41     ` Daniel Berlin
2009-06-27 15:19       ` Robert Dewar
2009-06-28  3:09     ` Ian Lance Taylor
2009-06-29 13:10       ` NightStrike
2009-06-29 13:13         ` Andrew Haley
2009-06-29 16:26         ` Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-25 20:33 Ian Lance Taylor
2009-06-25 21:39 ` Richard Guenther
2009-06-25 22:29 ` Joseph S. Myers
2009-06-25 22:47   ` Eric Botcazou
2009-06-25 22:49   ` Joe Buck
2009-06-26  7:09     ` Gabriel Dos Reis
2009-06-26 14:12       ` Jack Howarth
2009-06-26 18:21 ` Adam Nemet
2009-06-27 16:51 ` Adam Nemet
2009-06-27 18:07 ` David Edelsohn
2009-06-27 19:50   ` Sebastian Pop

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=206fcf960906290723r45f2db6fkaf44cf89e432e2bc@mail.gmail.com \
    --to=dosreis@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=iant@google.com \
    --cc=matt@use.net \
    --cc=nightstrike@gmail.com \
    --cc=richard.guenther@gmail.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).