RE: Get libffi closures to cope with SELinux execmem/execmod

[Andrew Haley <aph at redhat dot com>]

Boehm, Hans writes:
 > I'm still missing the big picture with respect to the finalization
 > changes.
 > 
 > Normally, the GC's intended usage model is that if I have an object P
 > whose finalizer accesses other referenced objects R, then I register P
 > with something like the "normal" finalization mark procedure, so that
 > the referenced objects R don't get finalized until P is done with them.
 > I think you are proposing to somehow have the objects R know that they
 > might be referenced by another finalizable object, and hence postpone
 > their own finalization by a cycle.  That seems fundamentally backwards
 > and brittle.  This just isn't R's business.
 > 
 > Can't we just register the referring object (P, the class in the real
 > case, I think) correctly?

For avoidance of doubt: I don't want any changes to be made to libgcj
until Hans' queries and objections have been satsified.

Andrew.