public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa][ GC, Virtual operands, and GCing between passes
Date: Thu, 11 Dec 2003 17:17:00 -0000	[thread overview]
Message-ID: <1071162566.10380.254.camel@p4> (raw)
In-Reply-To: <jmr7zbxpck.fsf@desire.geoffk.org>

On Thu, 2003-12-11 at 11:59, Geoff Keating wrote:
> Andrew MacLeod <amacleod@redhat.com> writes:
> 
> > I have array of pointers to trees.
> > 
> > so 
> > 
> > tree **defs;
> 
> That's an array of pointers to pointers to trees.  'tree' is a pointer
> to a tree.
> 

Depends on how you descibe it. 'tree' is a pointer to a tree
structure/union so  Its an array of pointers to pointers to tree
structures, yes, but an array of pointers to trees seemed like a
sufficient description to me... 

regardless, Its a cache of all the operand pointers in the stmt. So its
a list of pointers to trees so we can access/change them easily without
hunting for them. thus 'tree **'.

So all the trees will get marked when the stmt is marked. Since the
vector is part of the stmt annotation, if the stmt operands are not
marked, the annotation/vector will not get marked either. If the stmt is
marked, I need the vector to be marked, but none of the components.

So I need the tree ** vector to be treated as if is an array of
interegers or something, no marking of anything in it.

Im about to punt on it anyway and manage those vectors myself since GC
doesnt seem to want to deal with them nicely.

Andrew

  reply	other threads:[~2003-12-11 17:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 20:26 Andrew MacLeod
2003-12-09 23:43 ` Geoff Keating
2003-12-10  4:46   ` Andrew MacLeod
2003-12-11 17:01     ` Geoff Keating
2003-12-11 17:17       ` Andrew MacLeod [this message]
2003-12-11 21:15         ` Geoff Keating
2003-12-11 23:31           ` Andrew MacLeod
2003-12-15 22:05             ` Richard Henderson
2003-12-15 22:46               ` Andrew MacLeod
2003-12-11 19:30     ` law
2003-12-11 23:13       ` Andrew MacLeod
2003-12-12  0:21         ` law
2003-12-12  3:29           ` Andrew MacLeod
2003-12-12  5:24             ` law
2003-12-12 13:38               ` Andrew MacLeod
2003-12-13  6:52                 ` law
2003-12-11 14:17   ` Andrew MacLeod
2003-12-10  0:03 ` Jan Hubicka
2003-12-10  0:18   ` Andrew MacLeod
2003-12-10  0:38     ` Jan Hubicka
2003-12-11 19:30 ` law
2003-12-11 14:27 S. Bosscher
2003-12-11 14:34 ` Andrew MacLeod
2003-12-11 15:01   ` Andrew MacLeod

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=1071162566.10380.254.camel@p4 \
    --to=amacleod@redhat.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).