public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Geoffrey Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: GTY and const
Date: Tue, 21 Dec 2004 19:01:00 -0000	[thread overview]
Message-ID: <877jnbiih7.fsf@codesourcery.com> (raw)
In-Reply-To: <m2652vbj7w.fsf@greed.local> (Geoffrey Keating's message of "21 Dec 2004 10:26:59 -0800")

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.

zw

  reply	other threads:[~2004-12-21 19:01 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 [this message]
2004-12-22 23:11       ` Daniel Berlin
2004-12-22 23:24         ` Zack Weinberg
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=877jnbiih7.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --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).