| commit | c13436e516ed51bcc6f39b7b5c93d987e5fd7884 | [log] [tgz] |
|---|---|---|
| author | Kevin McAfee <kmcafee@nvidia.com> | Tue Apr 08 13:32:39 2025 -0700 |
| committer | GitHub <noreply@github.com> | Tue Apr 08 13:32:39 2025 -0700 |
| tree | 7df6d8e24d635130089f85914813cfdc797fdaee | |
| parent | 8b34986072d744009a4a2be9692b5cc43cbe4cd3 [diff] |
[SDAG][NVPTX] Add TLI hook to get preferred FP->INT opcode (#132470) Extract the logic for choosing FP_TO_UINT vs FP_TO_SINT opcodes into a TLI hook. This hook can be overridden by targets that prefer not to use the default behavior of replacing FP_TO_UINT with FP_TO_SINT when both are custom. Implement an override for NVPTX to only change opcode when FP_TO_UINT is not legal and FP_TO_SINT is legal.
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.