Shenandoah WB and XMM spills?
Aleksey Shipilev
shade at redhat.com
Thu Dec 14 16:53:21 UTC 2017
On 12/14/2017 05:42 PM, Roland Westrelin wrote:
> I'd like to push that patch as is. Ok?
We should protect things with UseShenandoahGC, I guess, because we would need to backport this
eventually? Also, do we want to additionally check the wb stub is only called with CallLeafNoFP? E.g.:
if (UseShenandoahGC && mcall->entry_point() == StubRoutines::shenandoah_wb_C()) {
assert(op == Op_CallLeafNoFP, "shenandoah_wb_C should be called with Op_CallLeafNoFP");
add_call_kills(proj, regs, save_policy, exclude_soe, true);
} else {
add_call_kills(proj, regs, save_policy, exclude_soe, false);
}
-Aleksey
More information about the shenandoah-dev
mailing list