Oh. I thought only the typeMonitorICs get garbage collected and the types added using the TypeScript::Monitor remain throughout the execution of the program. I believe this is what someone told me when I asked this question in the #jsapi irc channel. Can you suggest me how I can make these types persist across GC?
I am thinking of collecting the "no of times bailouts occur" heuristic in the first run and make compilation decisions in the second run. If there are too many bailouts during the execution of a function, there is no point compiling it with Ion right? Thanks, Madhukar N Kedlaya Graduate Student, University of California, Santa Barbara http://cs.ucsb.edu/~mkedlaya On Thu, Mar 5, 2015 at 6:52 AM, Nicolas B. Pierron < nicolas.b.pier...@mozilla.com> wrote: > On 03/05/2015 12:40 AM, Madhukar Kedlaya wrote: > >> Intuitively, feeding the type information should remove the bailouts in >> the >> subsequent runs. But I see a few of them still persisting. Any idea why >> this might be happening? >> > > 2 reasons: > - We might garbage collect the type info before starting a new collection > of types. > - The benchmark might not have a stable type info across time, and thus > the type info seen at the end of the benchmark does not match the type info > seen at the beginning of it. > > -- > Nicolas B. Pierron > > _______________________________________________ > dev-tech-js-engine-internals mailing list > dev-tech-js-engine-internals@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
