From: Zack Weinberg <zack@codesourcery.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Geoffrey Keating <geoffk@geoffk.org>, gcc@gcc.gnu.org
Subject: Re: GTY and const
Date: Wed, 22 Dec 2004 23:24:00 -0000 [thread overview]
Message-ID: <87zn06exoi.fsf@codesourcery.com> (raw)
In-Reply-To: <1103756747.20660.27.camel@linux.site> (Daniel Berlin's message of "Wed, 22 Dec 2004 18:05:47 -0500")
Daniel Berlin <dberlin@dberlin.org> writes:
> On Tue, 2004-12-21 at 11:01 -0800, Zack Weinberg wrote:
>> Geoffrey Keating <geoffk@geoffk.org> writes:
>>
>> >> > Would it be better to add a cast around the assignment or to make
>> >> > the GTY code handle const members?
>> >>
>> >> I'd prefer that you improved gengtype.
>> >
>> > It's not gengtype, the problem really is that you cannot have const
>> > GCed memory, for the same underlying reasons that you cannot free() a
>> > const pointer.
>>
>> No, that's just plain not true. cpplib makes extensive use of 'const'
>> to indicate write-once data structures (they are initialized through a
>> non-const pointer, of course). Those definitely can be GC memory.
>
> Right. There is a significant difference between what we need to walk
> for marking, and what we really need to GC allocate.
While what you say is true¹, this particular data structure needs to be
in GC memory not because it can point to other things that are in GC
memory, but because it's part of a precompiled header.
zw
¹ however, I am still sympathetic to the notion that GC-allocating
everything would be a good idea if we could just get a non-sucky GC
algorithm. Remember that glorious time in the 3.1-3.3 timeframe when
we never had use-after-free bugs?
next prev parent reply other threads:[~2004-12-22 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 7:00 Matt Kraai
2004-12-14 10:30 ` Steven Bosscher
2004-12-14 18:35 ` Zack Weinberg
2004-12-21 18:26 ` Geoffrey Keating
2004-12-21 19:01 ` Zack Weinberg
2004-12-22 23:11 ` Daniel Berlin
2004-12-22 23:24 ` Zack Weinberg [this message]
2004-12-23 3:43 ` Geoff Keating
2004-12-23 5:15 ` Zack Weinberg
2004-12-23 5:39 ` Daniel Berlin
[not found] <1103776856.24215.ezmlm@gcc.gnu.org>
2004-12-23 17:09 ` Lucas (a.k.a T-Bird or bsdfan3)
2004-12-23 20:04 ` Robert Dewar
2004-12-24 2:32 ` Marc Espie
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=87zn06exoi.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.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).