[mlir][spirv] Use `verifySymbolUses` for `spirv.FunctionCall`. (#159399) `spirv.FunctionCall`'s verifier was being too aggressive. It included verification of non-local properties by looking at the callee's definition. This caused problems in cases where callee had verification errors and could lead to null pointer dereferencing. According to [MLIR's developers guide ](https://mlir.llvm.org/getting_started/DeveloperGuide/#ir-verifier) > TLDR: only verify local aspects of an operation, > in particular don’t follow def-use chains > (don’t look at the producer of any operand or the user > of any results). The fix includes adding the `SymbolUserOpInterface` to `FunctionCall` and moving most of the verification logic to `verifySymbolUses`. Fixes #159295 --------- Co-authored-by: Jakub Kuderski <kubakuderski@gmail.com>
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.