Well, this probably could be turned on/off using a environment variable (something like OBJC_CYCLE_GC)... but the point is that the overhead shouldn't be that big; Inferno's algorithm was projected to do really small steps each time, so that it wouldn't have to suddenly stop-the-world as most GCs.
I'm still testing the runtime overhead on GNUStep, but I believe that the overhead will be really small. I would probably be able to test the same thing for Apple's as well (if I manage to build it from source...). Em 30/09/2015, às 00:09, Jens Alfke escreveu: > >> On Sep 29, 2015, at 8:00 PM, Paulo H. Taka Torrens <[email protected]> >> wrote: >> >> I've been working on an implementation of a concurrent garbage collector >> (based on Inferno's,http://doc.cat-v.org/inferno/concurrent_gc/) to warn the >> user and reclaim memory in cycles found in ARC during runtime for the >> GNUStep's Objective-C library. > > Is this as a debugging/performance tool? Or would it be incorporated in a > released app? It sounds like a lot of runtime overhead to add, just to add > the ability to free ref cycles. > > —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Objc-language mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/objc-language/archive%40mail-archive.com This email sent to [email protected]
