8264954: unified handling for VectorMask object re-materialization during de-optimization #3408
Following flow describes object reconstruction for de-optimization:-
By inserting a VectorStoreMaskNode before stitching the mask holding node to Safepoint we make sure that value held in opmask/vector register is transferred to a byte vector. Thus rest of the flow works as it is, stack location will hold the value in the form of a byte array irrespective of the box shape.
tier1-tier3 regressions are clean with UseAVX=2/3.
The text was updated successfully, but these errors were encountered:
@jatin-bhateja This change now passes all automated pre-integration checks.
After integration, the commit message for the final commit will be:
At the time when this comment was updated there had been 28 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
@jatin-bhateja Since your change was applied there have been 29 commits pushed to the
Your commit was automatically rebased without conflicts.
Pushed as commit f71be8b.