[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GC safety and return values

This page is part of the web mail archives of SRFI 50 from before July 7th, 2015. The new archives for SRFI 50 contain all messages, not just those from before July 7th, 2015.

>>>>> "Jim" == Jim Blandy <jimb@xxxxxxxxxx> writes:

Jim> But the thread-related problems with GCPRO that I don't see how
Jim> to solve are those created by the user's compiler rearranging
Jim> code that operates directly on heap references.  The compiler is
Jim> free to make copies of heap references in registers where a
Jim> copying GC can't find them to update them.

I don't think so---the typical GCPRO annotation (such as that in
Scheme 48) is going to take the address of the reference (which the
SRFI allows) which limits the compiler's ability to do such things
exactly in the way desired.

(This isn't a comment on the general issue, just on this specific

Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla