[HIP] Fix ubsan function checks applied to kernel functions (#188872) Summary: The 'function' check requires inserting eight bytes of magic before each function. The HIP runtime expects and enforces 256 byte alignment. When the instrumentation inserts the eight bytes this is done after the alignment, which means that the HIP runtime then points the PC to an invalid instruction by truncating the address to 256 byte alignment. The OpenMP runtime doesn't do this. The purpose of this function is to handle indirect calls, and it's impossible to indirectly call a kernel anyway, so we should just suppress this in this case. The only other solution would be to add the alignment back before we emit the label, but that would be meaningless because it'd just replace the magic bytes with zeroes.
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.