[bazel] Gate GPU parsers behind llvm_targets#187213
Conversation
Ideally fixes llvm#63135 Signed-off-by: Vimarsh Sathia <vsathia2@illinois.edu>
|
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 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. |
|
@boomanaiden154 @j2kun @aaronmondal can one of you guys review this |
boomanaiden154
left a comment
There was a problem hiding this comment.
This seems fine to me assuming you've validated that the build works with just NVPTX, with just AMDGPU, and with neither.
|
Yes, I validated it with an updated version of the mlir tutorial here (my version builds without enabling NVPTX and AMDGPU there) |
Signed-off-by: Vimarsh Sathia <vsathia2@illinois.edu>
|
Ah I didnt run buildifier |
|
@rupprecht can you approve again (sorry it seems like the CI run got cancelled) |
|
seems like my buildifier and the expected one arent the same |
Until llvm/llvm-project#187213 gets in
Until llvm/llvm-project#187213 gets in
|
@rupprecht : github has once again decided swapping 2 lines is a profound change - can you re-approve this? |
|
@vimarsh6739 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! |
When llvm/llvm-project#187213 lands, removing these lines should no longer break the build PiperOrigin-RevId: 886363233
When llvm/llvm-project#187213 lands, removing these lines should no longer break the build PiperOrigin-RevId: 886363233
When llvm/llvm-project#187213 lands, removing these lines should no longer break the build PiperOrigin-RevId: 886363233
When llvm/llvm-project#187213 lands, removing these lines should no longer break the build PiperOrigin-RevId: 886363233
When llvm/llvm-project#187213 lands, removing these lines should no longer break the build PiperOrigin-RevId: 888142864
Ideally fixes #63135