In JDK-8304389 we fixed a regression in 11u with basically undoing a previous change (JDK-8248238) that just made the issue appear. We needed a quick-fix before delivering 11.0.19. See JDK-8304389 for details.
It seems the issue is fixed differently in recent JDKs (16+), at least it can not be reproduced there. But potentially C2 just generates different code in 16+ so that the issue can not be reproduced with the same test. Unfortunately the test is an SAP internal one.
Find the root cause and fix it.
As it is not clear whether the root cause is fixed in 16+ I do not assign this to 11u only.