This is a bug fix for further issues in PR43585.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
lgtm
llvm/test/CodeGen/X86/win64-funclet-savexmm.ll | ||
---|---|---|
92 | So, this was wrong, it was storing to memory at RSP+[80-96], which would overwrite pushq %rbx from above. Yikes. |
Comment Actions
I don't know if there is a separate list of committers who can push to the release/9.x branch. I'd suggest trying it. Merging should be a matter of doing the following:
$ git pull # make sure up to date $ git checkout release/9.x # check out current 9.0.1 release, typically slow $ git cherry-pick -x ${githash} # cherry pick this patch. -x adds a note about the original hash. $ git push ${remote} release/9.x # push to the llvm github remote release/9.x branch
Fill in appropriate values of githash and remote. If it doesn't work, I'll give it a shot next week.
Thanks for following up! Bugs happen.
Comment Actions
Anyone can commit to the release branch, yes, but nobody is supposed to unless the release manager approves. See http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules .
I guess with the move to GitHub, we could start applying per-branch permissions to enforce that?
So, this was wrong, it was storing to memory at RSP+[80-96], which would overwrite pushq %rbx from above. Yikes.