[aarch64-port-dev ] RFR 8233339: Shenandoah: Centralize load barrier decisions into ShenandoahBarrierSet
aph at redhat.com
Fri Nov 1 10:15:37 UTC 2019
On 10/31/19 6:48 PM, Zhengyu Gu wrote:
> Right now, the decisions on, if a load barrier needs load reference
> barrier, if so, what kind? and if the reference needs to be kept alive,
> are scattered inside interpreter/c1/2 load barrier code, which is hard
> to make them consistent.
> I would like to centralize the decision making into
> ShenandoahBarrierSet, so them can be consistent and easy to maintain.
You should say, at the start of every routine you touch, which
registers are inputs, which are outputs, and (important) which may
alias with rscratch1 and rscratch2. Please also mark clobbers of
rscratch1 and 2.
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the hotspot-gc-dev