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
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
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?
Comment Actions
The pre-commit test failure is also failing on the buildbots, not related to this patch.
clang-format: please reformat the code