This is an archive of the discontinued LLVM Phabricator instance.

[ARM] Track epilogue instructions with FrameDestroy flag (NFC)
ClosedPublic

Authored by ostannard on Nov 6 2019, 9:43 AM.

Details

Summary

Rather than trying to work out which instructions are part of the epilogue by examining them, we can just mark them with the FrameDestroy flag, like we do in the AArch64 backend.

Diff Detail

Unit TestsFailed

Event Timeline

ostannard created this revision.Nov 6 2019, 9:43 AM
Herald added a project: Restricted Project. · View Herald TranscriptNov 6 2019, 9:43 AM
tellenbach removed a subscriber: tellenbach.
tellenbach added a subscriber: tellenbach.
ostannard updated this revision to Diff 250200.Mar 13 2020, 7:31 AM
ostannard added a reviewer: efriedma.
  • Rebase
  • Fix an MIR test

I don't really want to sort of halfheartedly add frame-destroy markings where they're locally convenient, and have it be sort of random which epilogue instructions actually have the markings after PEI. How much work would it be to actually mark everything, like we do on AArch64?

ostannard updated this revision to Diff 250519.Mar 16 2020, 4:32 AM
  • Add frame-destroy flag to every instruction in epilogue.

The pre-commit test failure is also failing on the buildbots, not related to this patch.

This revision is now accepted and ready to land.Mar 16 2020, 12:11 PM