| commit | be587941c22f16df6fb2053cc06cf91c5a378613 | [log] [tgz] |
|---|---|---|
| author | Jakub Kuderski <jakub@nod-labs.com> | Fri Sep 12 11:32:10 2025 -0400 |
| committer | GitHub <noreply@github.com> | Fri Sep 12 11:32:10 2025 -0400 |
| tree | a100be1911d58b630d5b87fd64cd98f0a8fbe9b7 | |
| parent | 149f91bad66972ad8bf0add5c79bf74055f6905a [diff] |
[mlir] Self-nominate for arith dialect maintenance (#157355) Following https://llvm.org/docs/DeveloperPolicy.html#maintainers, I'd like to self-nominate for arith dialect maintenance. As per the policy: > Maintainers are volunteering to take on the following shared responsibilities within an area of a project: > ... I believe I've been already performing most of the maintenance duties over the past few years, including direct code contributions, code reviews, and both starting and participating in relevant RFCs on discourse. You can look those up with: * `git log --author=Jakub --oneline -- 'mlir/include/mlir/Dialect/Arith*' 'mlir/lib/Dialect/Arith*'` * https://github.com/llvm/llvm-project/pulls?q=is%3Apr+label%3Amlir%3Aarith+reviewed-by%3Akuhar * Some notable RFCs authored: https://discourse.llvm.org/t/rfc-define-precise-arith-semantics/65507, https://discourse.llvm.org/t/rfc-poison-semantics-for-mlir/66245, https://discourse.llvm.org/t/rfc-arith-add-extended-multiplication-ops/66869, https://discourse.llvm.org/t/rfc-add-integer-add-with-carry-op-to-arith/64573, https://discourse.llvm.org/t/rfc-arith-should-we-support-scalar-vector-arith-bitcast-s/65427. In addition to the `core` category maintainers, I can bring additional perspective as I care both about conversion to llvm (as a user) and to spirv (as a maintainer).
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.