Page MenuHomePhabricator

[Statepoint] Factor-out utility function to get non-foldable area of STATEPOINT like instructions. NFC

Authored by skatkov on Mon, Apr 5, 12:01 AM.

Diff Detail

Event Timeline

skatkov created this revision.Mon, Apr 5, 12:01 AM
skatkov requested review of this revision.Mon, Apr 5, 12:01 AM
Herald added a project: Restricted Project. · View Herald TranscriptMon, Apr 5, 12:01 AM
skatkov added inline comments.Mon, Apr 5, 2:07 AM

to be honest, not happy with the name.
Actually I also want to use this function to determine what operands are ok to use both stack and register...
Any suggestions for the name?

reames requested changes to this revision.Mon, Apr 5, 8:41 AM

Naming suggestions, but likely to converge to LGTM on next iteration.


Minor, move the assert above the variable declarations.

This revision now requires changes to proceed.Mon, Apr 5, 8:41 AM
reames added a comment.Mon, Apr 5, 8:46 AM

For unclear reasons, phab dropped a long inline comment from my previous review. Rewritten here.

The comment and naming was confusing to me. I'd suggest the following changes.

  1. Restrict the API and naming to patchpoint, stackmap, and statepoint explicitly.
  2. Be clear about the fact that operands are "potentially foldable", not "guaranteed foldable".

A suggested name and comment: getPatchpointUnfoldableRange.

For a patchpoint, stackmap, or statepoint intrinsic, return the range of operands which can't be folded into stack references. These instructions are unique in that stack references for some operands have the same execution cost (e.g. none) as the unfolded register forms. The ranged return is guaranteed to include all operands which can't be folded at zero cost.

skatkov updated this revision to Diff 335392.Mon, Apr 5, 9:10 PM

Handled Philip's omments.

Philip, thank you for your phrasing suggestions.

reames accepted this revision.Mon, Apr 5, 9:13 PM


This revision is now accepted and ready to land.Mon, Apr 5, 9:13 PM