On Fri, 26 Apr 2024 08:45:45 GMT, Claes Redestad wrote:
>> Splitting out the ASM-based version from #18690 to push that first under the
>> JBS (to help backporting). Keeping #18690 open to rebase and follow-up on
>> this as a subtask. See discussion in that #18690 for more details,
>> discussi
On Fri, 26 Apr 2024 08:45:45 GMT, Claes Redestad wrote:
>> Splitting out the ASM-based version from #18690 to push that first under the
>> JBS (to help backporting). Keeping #18690 open to rebase and follow-up on
>> this as a subtask. See discussion in that #18690 for more details,
>> discussi
> Splitting out the ASM-based version from #18690 to push that first under the
> JBS (to help backporting). Keeping #18690 open to rebase and follow-up on
> this as a subtask. See discussion in that #18690 for more details, discussion
> and motivation for this.
Claes Redestad has updated the pu
On Fri, 12 Apr 2024 15:06:36 GMT, Chen Liang wrote:
>> I'd prefer considering such optimizations as follow-ups. We need to think
>> about where to define such shared classes in a way that considers the full
>> lifecycle, facilitates class unloading (one cache per classloader?) while
>> still g
> This patch suggests a workaround to an issue with huge SCF MH expression
> trees taking excessive JIT compilation resources by reviving (part of) the
> simple bytecode-generating strategy that was originally available as an
> all-or-nothing strategy choice.
>
> Instead of reintroducing a bin
On Sat, 13 Apr 2024 17:54:54 GMT, Brett Okken wrote:
>> Possibly. I tried a few simple variants that initialized the `StringBuilder`
>> capacity at various guesses, such as sum of constant sizes + some factor
>> based on args, but across a diverse set of micros that gives both some wins
>> and
