> 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. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai).
Galder Zamarreño has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains two additional commits since the last revision: - Merge branch 'master' into topic.clipping-overflow - Fix highest int/log values, they were overflowing ------------- Changes: - all: https://git.openjdk.org/jdk/pull/30115/files - new: https://git.openjdk.org/jdk/pull/30115/files/14a536d0..44f4d378 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=30115&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30115&range=00-01 Stats: 2060998 lines in 17022 files changed: 1182598 ins; 700045 del; 178355 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
