Fixed benchmark code to avoid overflowing when calculating `highestInt` and `highestLong`.
I observed this during early benchmark runs of https://github.com/openjdk/jdk/pull/30070. I observed some oddities in the results with the clipping range benchmarks, and when I inspected the assembly, the values that were being used to clip didn't make sense. After fixing this the odd results went away. ------------- Commit messages: - Fix highest int/log values, they were overflowing Changes: https://git.openjdk.org/jdk/pull/30115/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=30115&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8364025 Stats: 2 lines in 1 file changed: 0 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/30115.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/30115/head:pull/30115 PR: https://git.openjdk.org/jdk/pull/30115
