Closed csstormq closed 5 months ago
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this page.
If this is not working for you, it is probably because you do not have write
permissions for the repository. In which case you can instead tag reviewers by
name in a comment by using @
followed by their GitHub username.
If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.
If you have further questions, they may be answered by the LLVM GitHub User Guide.
You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.
@llvm/pr-subscribers-backend-x86
Author: None (csstormq)
Looks like a straightforward fix to me. Is there any way to add a unit test?
Thanks, @atrick . I have added a test in X86 target, as you suggested. Please review again, thank you.
@csstormq Congratulations on having your first Pull Request (PR) merged into the LLVM Project!
Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.
Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.
How to do this, and the rest of the post-merge process, is covered in detail here.
If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.
If you don't get any reports, no action is required from you. Your changes are working as expected, well done!
This seems to break tests: http://45.33.8.238/linux/138572/step_11.txt
Please take a look and revert for now if it takes a while to fix.
This seems to break tests: http://45.33.8.238/linux/138572/step_11.txt
Please take a look and revert for now if it takes a while to fix.
OK. I will now check whether problems have been caused by my change. Please wait a moment.
This seems to break tests: http://45.33.8.238/linux/138572/step_11.txt
Please take a look and revert for now if it takes a while to fix.
Hi, @nico . I have created an new pull request #92992 to revert this commit. Please approve it, thank you.
ppc AIX/Linux buildbots also fail at the same cases. https://lab.llvm.org/buildbot/#/builders/57/builds/35165 https://lab.llvm.org/buildbot/#/builders/214/builds/12263
ppc AIX/Linux buildbots also fail at the same cases. https://lab.llvm.org/buildbot/#/builders/57/builds/35165 https://lab.llvm.org/buildbot/#/builders/214/builds/12263
@AtariDreams has addressed these broken unit tests. I would like to rebase our commits to one if possible.
…cal path consistently
Fix https://github.com/llvm/llvm-project/issues/38037