Unsafe vs MemorySegments / Bounds checking...

[Brian S O'Neill]

> 
> 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.