On Thu, 27 Jun 2024 14:12:36 GMT, Shaojin Wen wrote:
>> Currently, the java.util.Formatter$Conversion::isValid method is implemented
>> based on switch, which cannot be inlined because codeSize > 325. This
>> problem can be avoided by implementing it with ImmutableBitSetPredicate.
>>
>> use `-
> Currently, the java.util.Formatter$Conversion::isValid method is implemented
> based on switch, which cannot be inlined because codeSize > 325. This problem
> can be avoided by implementing it with ImmutableBitSetPredicate.
>
> use `-XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining` to see the
On Thu, 27 Jun 2024 11:48:56 GMT, Shaojin Wen wrote:
> * byte codes of `Conversion.isValid`
It's surprising that javac generates synthetic cases identical to the default
case for every char in the 37 to 120 range (the bounds seem to be the lowest
and highest of the constants).
Is there a ben
On Thu, 27 Jun 2024 11:14:30 GMT, Shaojin Wen wrote:
> Currently, the java.util.Formatter$Conversion::isValid method is implemented
> based on switch, which cannot be inlined because codeSize > 325. This problem
> can be avoided by implementing it with ImmutableBitSetPredicate.
>
> use `-XX:+U
Currently, the java.util.Formatter$Conversion::isValid method is implemented
based on switch, which cannot be inlined because codeSize > 325. This problem
can be avoided by implementing it with ImmutableBitSetPredicate.
use `-XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining` to see the master
b
