Re: SwitchPoint strategy for JRuby class modification invalidation

2011-05-26 Thread Charles Oliver Nutter
On Thu, May 26, 2011 at 9:02 PM, John Rose wrote: > Fully optimized invalidations will use safepoints.  The point of using an > array is to allow any number of switchpoints to ride on one safepoint.  Can > you batch all the invalidations in a given hierarchy of N classes?  Or is > there an orde

Re: SwitchPoint strategy for JRuby class modification invalidation

2011-05-26 Thread John Rose
That sounds right. On May 26, 2011, at 6:31 PM, Charles Oliver Nutter wrote: > * For a descendant hierarchy of N classes, I'll need to do N > invalidateAll calls. This is not ideal, since those calls are very > heavy. Fully optimized invalidations will use safepoints. The point of using an arra

SwitchPoint strategy for JRuby class modification invalidation

2011-05-26 Thread Charles Oliver Nutter
I wanted to outline how I plan to make JRuby's current class modification check eventually be all SwitchPoint driven. JRuby, like some other dynamic languages, allows runtime modification of pretty much every class in the system. Usually this only happens at boot time, but since it can potentially