Brendan Eich wrote: > Jonas Sicking wrote: >> Related to the above, should we attempt to use incremental GC. From what >> I understand this should be entierly possible with MMgc. However it >> requires that all pointers use special smart-pointers. Including >> pointers that are currently raw-pointers. This seems a little bit >> scary and easy to forget, but might be very nice for performance. > > Raw pointers should be banned in incremental GC settings. We can use > static analysis to enforce this.
Sorry to be unclear: the context here is heap-allocated data structures. You need a write barrier for any pointer in another GC-allocated struct. The thread stack can be full of raw pointers, no problem. Conservative scanning means they (along with the odd float ;-) will be taken for strong refs, and mutation does not need to update card marks or colors since we don't GC the stack. /be _______________________________________________ dev-tech-xpcom mailing list dev-tech-xpcom@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-xpcom
