| commit | acde3f722ff3766f6f793884108d342b78623fe4 | [log] [tgz] |
|---|---|---|
| author | Peter Hawkins <phawkins@google.com> | Fri Jan 24 09:26:28 2025 -0500 |
| committer | GitHub <noreply@github.com> | Fri Jan 24 06:26:28 2025 -0800 |
| tree | 61d63b9df44ccf448952791363d8a869cb8df651 | |
| parent | 77c780d64b950d6850d5ec1ee06cd0c21b38b89e [diff] |
[mlir:python] Compute get_op_result_or_value in PyOpView's constructor. (#123953) This logic is in the critical path for constructing an operation from Python. It is faster to compute this in C++ than it is in Python, and it is a minor change to do this. This change also alters the API contract of _ods_common.get_op_results_or_values to avoid calling get_op_result_or_value on each element of a sequence, since the C++ code will now do this. Most of the diff here is simply reordering the code in IRCore.cpp.
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.