Unsafe vs MemorySegments / Bounds checking...

[Jorn Vernee]

On 29-10-2024 20:22, Brian S O'Neill wrote:
>
>>
>> If you have a better benchmark, or you can pin point the exact place 
>> where the inlining failure occurs that would help immensely. You can 
>> play around with CompileCommand and force inline for specific methods 
>> of your application. (perhaps after verifying that such methods are 
>> not inlined, which you can verify with -XX:+PrintInlining).
>>
>
> How do I force inlining? I thought this was only possible the internal 
> HotSpot annotation.


See the output of 'java -XX:CompileCommand=help' (look at the output 
before the standard help message). To force inlining of a method into 
other compilation units you would use something like 
`-XX:CompileCommand=inline,xyz.MyClass::myMethod`.

Jorn