Re: RFR: 8245094: Reduce overhead of initializing the default StringConcatFactory strategy

Thanks, Paul! /Claes On 2020-05-15 18:00, Paul Sandoz wrote: +1 Paul. On May 15, 2020, at 3:54 AM, Claes Redestad wrote: Hi, by adding a bridge method in JavaLangAcces to call into the StringConcatHelper.initialCoder - which is done only once during initialization - we can reduce

Re: RFR: 8245094: Reduce overhead of initializing the default StringConcatFactory strategy

+1 Paul. > On May 15, 2020, at 3:54 AM, Claes Redestad wrote: > > Hi, > > by adding a bridge method in JavaLangAcces to call into the > StringConcatHelper.initialCoder - which is done only once during > initialization - we can reduce bootstrap overhead of SCF by a few > million instructions -

Re: RFR: 8245094: Reduce overhead of initializing the default StringConcatFactory strategy

On 2020-05-15 13:53, Jim Laskey wrote: +1 Thanks, Jim! /Claes On May 15, 2020, at 7:54 AM, Claes Redestad wrote: Hi, by adding a bridge method in JavaLangAcces to call into the StringConcatHelper.initialCoder - which is done only once during initialization - we can reduce bootstrap

Re: RFR: 8245094: Reduce overhead of initializing the default StringConcatFactory strategy

+1 > On May 15, 2020, at 7:54 AM, Claes Redestad wrote: > > Hi, > > by adding a bridge method in JavaLangAcces to call into the > StringConcatHelper.initialCoder - which is done only once during > initialization - we can reduce bootstrap overhead of SCF by a few > million instructions -

RFR: 8245094: Reduce overhead of initializing the default StringConcatFactory strategy

Hi, by adding a bridge method in JavaLangAcces to call into the StringConcatHelper.initialCoder - which is done only once during initialization - we can reduce bootstrap overhead of SCF by a few million instructions - ~0.5ms on wall clock measures. Webrev: