Resolve issues around identifying end/beginning of callee-save spill/restore
@asb is already working on this.
Since Aug 20, 2017.
- Dominant language
- Shell
- Stars
- 277
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
A hacky patch in PrologEpilogInserter is currently used (see [here](https://github.com/lowRISC/riscv-llvm/blob/master/0020-Hack-Set-Frame-Setup-Destroy-in-PrologEpilogInserter.patch)). I posted an [RFC](http://lists.llvm.org/pipermail/llvm-dev/2017-February/110281.html) and [illustrative patch](https://reviews.llvm.org/D30115) for fixing this issue in a cleaner way. After further discussion, I [now believe](http://lists.llvm.org/pipermail/llvm-dev/2017-February/110351.html) that relying on debug info for determining the callee-save spill/restore end/beginning may not be the best approach.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.