I'm also interested. Especially, what statistical information need to be collected at call site to effectively switch between mono/poly/megamorphic cache.
2009/3/6 Jecel Assumpcao Jr <[email protected]>: > I am interested in the various efforts to add Polymorphic Inline Caches > to Squeak, like in > >> slides - http://www.iam.unibe.ch/~denker/talks/07ICOOLPS/07PICsICOOOLPS.pdf > >> paper - >> http://www.hirschfeld.org/misc/media/HauptHirschfeldDenker_2007_TypeFeedbackForBytecodeInterpreters.pdf > > For this design they just replace the pointer to the symbol in the > method's literal frame with a pointer to an object which then points to > that symbol and which also adds the needed information (class / compiled > method pairs). > > I plan to browse the Exupery sources to see what its PICs are like, but > for now I just took a quick look at the various presentations that are > available and saw a thread on this list from October 2008. My impression > so far is that PICs are short code fragments with pointers to classes > and which are treated mostly like native methods. > > If there are more details anywhere, it would be very helpful. > -- Jecel > > _______________________________________________ > Exupery mailing list > [email protected] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Exupery mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery
