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: Wed, 10 Dec 2003 04:46:00 -0000 [thread overview]
Message-ID: <1071016677.17667.2918.camel@p4> (raw)
In-Reply-To: <jmzne1y350.fsf@desire.geoffk.org>
On Tue, 2003-12-09 at 18:36, Geoff Keating wrote:
> Andrew MacLeod <amacleod@redhat.com> writes:
>
> > Are we sure we want to GC between passes? :-|
> >
> > since VDEFs and VUSEs are tree nodes, I can't allocate the structure
> > which holds them anywhere except GC'd memory can I?
> >
> > ie
> >
> > a_3 = VDEF <a_2>
> >
> > This requires points to 2 trees.
> >
> > the GC system has to know not to collect the trees I am pointing to in
> > the 2 words of the vdef vector.
> >
> > but I dont want to GC the vdef vector.
>
> Why not?
>
Ok, so assuming I do it all in GCable form,
I have array of pointers to trees.
so
tree **defs;
I don't want what defs points to to be marked, since they are marked
otherwise, I just need the defs vector itself collected:
typedef struct def_optype_d GTY(())
{
unsigned num_defs;
tree ** GTY((skip(""))) defs;
} def_optype_t;
If I use skip like this, it doesnt do anything does it? meaning it
doesnt free defs?
typedef struct def_optype_d GTY(())
{
unsigned num_defss;
tree **GTY((length ("%h.num_defs"))) defs;
} vdef_optype_t;
I can tell it how long the vector is but then it claims it doesnt
understand the type "tree **", so it aborts.
Should it look like:
typedef struct def_optype_d GTY(())
{
unsigned num_defs;
tree ** GTY((length ("%h.num_vuses"),skip(""))) defs;
} def_optype_t;
or what do I need to do?
Andrew
next prev parent reply other threads:[~2003-12-10 0:38 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 [this message]
2003-12-11 17:01 ` Geoff Keating
2003-12-11 17:17 ` Andrew MacLeod
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=1071016677.17667.2918.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).