RFR(M): 8213528: fp registers should not need to be saved around a CallLeafNoFP

Roland Westrelin rwestrel at redhat.com
Thu Nov 8 11:01:06 UTC 2018


Currently CallLeafNoFP and CallLeaf don't differ in any way. My
understanding is that CallLeafNoFP should give the guarantee that it
leaves fp registers untouched and so fp registers shouldn't be saved
around a CallLeafNoFP. That's what this change implements. To be on the
safe side, all CallLeafNoFP calls are turned into CallLeaf and existing
behavior is preserved. That's another change motivated by Shenandoah
where we have a use for this.


More information about the hotspot-compiler-dev mailing list