RFR: 8348855: G1: Implement G1BarrierSetC2::estimate_stub_size [v2]
Aleksey Shipilev
shade at openjdk.org
Thu Jan 30 11:58:04 UTC 2025
> We run into peculiar problem in Leyden: due to current prototype limitation, we cannot yet store the generated code that has the expanded code buffer. The code buffer expansion routinely happens with late G1 barrier expansion, as `G1BarrierSetC2` does not report any estimate for stub sizes.
>
> So a method rich in these G1 stubs would blow the initial code size estimate, force the buffer resize, and thus disqualify itself from storing C2 code in Leyden. Whoops. Fortunately, we just need to implement `G1BarrierSetC2::estimate_stub_size()` in mainline to avoid a significant part of this problem.
>
> I also fixed the misattribution of "stub" sizes in insn section, this part is also important to get the stub sizes right. I can do that separately, but it would only matter for ZGC without G1 stub size estimation implemented.
>
> You can see the impact it has on Leyden here:
> https://github.com/openjdk/leyden/pull/28#issuecomment-2619077625
>
> Additional testing:
> - [x] Linux x86_64 server fastdebug, `all`
> - [x] Linux AArch64 server fastdebug, `all`
Aleksey Shipilev has updated the pull request incrementally with one additional commit since the last revision:
Revert Leyden-specific additions, plainly estimate the stubs size
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/23333/files
- new: https://git.openjdk.org/jdk/pull/23333/files/bec7c5c1..41950b7f
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=23333&range=01
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=23333&range=00-01
Stats: 5 lines in 2 files changed: 0 ins; 3 del; 2 mod
Patch: https://git.openjdk.org/jdk/pull/23333.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/23333/head:pull/23333
PR: https://git.openjdk.org/jdk/pull/23333
More information about the hotspot-dev
mailing list