ADDITIONAL SYSTEM INFORMATION :
Microsoft Windows 10 Professional
10.0.19044 Build 19044
AMD Ryzen 5 5600G with Radeon Graphics 3.90 GHz
Memory 32 GB

openjdk version "1.8.0_322"
OpenJDK Runtime Environment BiSheng (build 1.8.0_322-b06)
OpenJDK 64-Bit Server VM BiSheng (build 25.322-b06, mixed mode)

openjdk version "11.0.14" 2022-01-18
OpenJDK Runtime Environment BiSheng (build 11.0.14+9)
OpenJDK 64-Bit Server VM BiSheng (build 11.0.14+9, mixed mode)

A DESCRIPTION OF THE PROBLEM :
When we try to execute the test case using Hotspot, we may get incorrect output. In the test case, we executed the checksum 100,000 times, so we got the correct output of 98900000. But when we execute the test case using Hotspot, the output is 98900989.
In addition, we also tried to set the -Xint tag at execution, and we could get the correct output. So we think the issue may be related to JIT optimization

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :

The current issue can be replicated in both JDK8 and JDK11.
hotspot8/bin/java testCase12
hotspot8/bin/java -Xint testCase12
hotspot11/bin/java testCase12
hotspot11/bin/java -Xint testCase12

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
98900000
98900000
98900000
98900000
ACTUAL -
98900989
98900000
98900989
98900000

FREQUENCY : always