Is the gcc garbage collector compacting?
In particular I want to have ".def" file (like tree.def) where
the macros generate struct declarations,
and the fields might be tree.
That won't work with the gcc garbage collection scheme.
However, I'm willing also store all trees
that go in these structs in a global VEC of trees,
that does work with the garbage collector.
That would suffice to keep them alive.
But it wouldn't keep them up to date if the
garbage collector is compacting.
Heck, I guess, if need be, I'm willing to apply
a slight hack to disable the garbage collector.
If I really must -- if there is really much garbage
to collect, I could run the preprocessor ahead of time
and provide a file to gengtype that it understands.
I'm leary of this approach, because I want only
certain preprocessing to take place.
I could output markers before/after the chunk I want though.
Or, maybe the files do get preprocessed?
Evidence is no, as when #if 0'ed out some types, gengtype still saw them.
Something to consider, perhaps.
Thanks,
- Jay
