Skip to content

[bazel] Add missing targets for CIR - #220753

Open
vsytch wants to merge 1 commit into
llvm:mainfrom
vsytch:cir-bazel-support
Open

[bazel] Add missing targets for CIR#220753
vsytch wants to merge 1 commit into
llvm:mainfrom
vsytch:cir-bazel-support

Conversation

@vsytch

@vsytch vsytch commented Sep 2, 2026

Copy link
Copy Markdown

[bazel] Add missing targets for CIR

Add Bazel build support for ClangIR (CIR) dialects, interfaces, passes,
transformations, and code generation under `utils/bazel`:

1. In `llvm-project-overlay/clang/BUILD.bazel`:
   - Add TableGen targets (`:CIRTdFiles`, `:MLIRCIROpsIncGen`,
     `:MLIRCIREnumsGen`, `:CIRLowering`, `:MLIRCIRTypeConstraintsIncGen`,
     `:MLIRCIRPassIncGen`, `:MLIRCIRASTAttrInterfacesIncGen`,
     `:MLIRCIROpInterfacesIncGen`, `:MLIRCIRLoopOpInterfaceIncGen`,
     `:MLIRCIRTypeInterfacesIncGen`).
   - Add CIR C++ libraries (`:cir_headers`, `:cir_interfaces`,
     `:cir_dialect`, `:cir_openacc_support`, `:cir_openmp_support`,
     `:cir_all_dialects`, `:cir_analysis`, `:cir_target_lowering`,
     `:cir_transforms`, `:cir_codegen`, `:cir_lowering_common`,
     `:cir_lowering_direct_to_llvm`, `:cir_frontend_action`).
2. In `llvm-project-overlay/mlir/BUILD.bazel`:
   - Add `:ABI` library target (`MLIRABI`).
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Hello @vsytch 👋

Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this is your first PR, here are a few useful links covering our main contribution policies and review practices.

  • All contributions to LLVM must follow our LLVM AI Tool Use Policy. In particular, if you used AI while working on this PR, remember to add a note to the PR description.
  • The LLVM Code-Review Policy and Practices document contains practical information about the PR process, including how patches are reviewed and accepted, and who can review a PR.
  • Our LLVM Developer Policy describes our expectations for code quality, commit summaries and contains notes on our CI system.

Please reply to this message to confirm that you have read these policies, especially the LLVM AI Tool Use Policy, and that any AI tool usage has been noted in the PR description.


Frequently asked questions

How do I add reviewers?

This PR will be automatically labeled, and the relevant teams will be notified. For some parts of the project, reviewers may also be added automatically.

You can also add reviewers manually using the Reviewers section on this page. If you cannot use that section, it is probably because you do not have write permissions for the repository. In that case, you can request a review by tagging reviewers in a comment using @ followed by their GitHub username.

What if there are no comments?

If you have not received any comments on your PR after a week, you can request a review by pinging the PR with a comment such as “Ping”. The common courtesy ping rate is once a week. Please remember that you are asking for volunteer time from other developers.

Are any special GitHub settings required to contribute to LLVM?

We only require contributors to have a public email address associated with their GitHub commits, see this section of LLVM Developer Policy for details.


If you have questions, feel free to leave a comment on this PR, or ask on LLVM Discord or LLVM Discourse.

Thank you,
The LLVM Community

@llvmorg-github-actions llvmorg-github-actions Bot added the bazel "Peripheral" support tier build system: utils/bazel label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bazel "Peripheral" support tier build system: utils/bazel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant