Template interpreter implements class initialization barriers for putstatic/getstatic instructions by deferring instruction resolution until corresponding field holder class is fully initialized. It results in repeated re-resolution calls into interpreter runtime during <clinit> execution and may noticeably slow down application startup.
Instead, a fast class initialization check in template interpreter generated code for putstatic/getstatic instructions would do the job in a much more performant way.
Instead, a fast class initialization check in template interpreter generated code for putstatic/getstatic instructions would do the job in a much more performant way.