This is the mail archive of the mailing list for the Archer project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [python] don't try to free "independent" types

El mar, 25-11-2008 a las 15:32 -0700, Tom Tromey escribiÃ:
> Reference counting for types referred to by values would be handled in
> allocate_value and a small number of other places.
> Then we'd need some additional code to register new types created by
> things like make_pointer_type.  This is probably the time-consuming bit.
> Perhaps it could be done by changing alloc_type.

Some type hierarchies are also created in places that call

Also, IIUC you'd need some checks to avoid freeing builtin_types, and
types created by each language, and types created by each architecture
which they use for their fancy registers, and other eventual types which
are not initially associated with an objfile.

Is it possible that one struct type can be present in two hierarchies?
>From some initial thinking, I believe this can only happen for the
special cases I mentioned above.
Thiago Jung Bauermann
IBM Linux Technology Center

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]