Yep and if 50% of objects are value types and 50% of the ref objects/actions are in enclosed regions there should only be 25% of the ref counts ... 12% basic interlock ref count system cost becomes 3% .
When i wrote that i was thinking reference could be 11-12 bytes structures with the pointer ( or possibly masked high bits in a 64 bit pointer or 32 bit pointer as an option on a 64 bit machine) and some flags (freeze / release immutable ) and a counter so you dont have to have a header. This is not possible in Java not because of value types ( stupid of me) but because you cant get wrid of the header without a completely new Runtime . You could measure the impact of 11-12 byte pointers but not the cost of removing the header . Ben On Tue, Oct 15, 2013 at 12:34 PM, Jonathan S. Shapiro <[email protected]>wrote: > On Mon, Oct 14, 2013 at 9:24 PM, Bennie Kloosteman <[email protected]>wrote: > >> I suspect on value type system a seperate field is much faster as unlike >> Java you dont have the header cost on everything... >> > > Except that you'll never see a counted reference to a value type. > > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
