llvm with tablegen backend for capstone disassembler
Go to file
Craig Topper e82d2e8c11 Recommit "[Sema] Fix null pointer dereference handleAlwaysInlineAttr."
Remove use of constexpr if that failed on the build bots.

Original commit message:

It's possible for `getCalleeDecl()` to return a null pointer.

This was encountered by a user of our downstream compiler.

The case involved a DependentScopeDeclRefExpr.

Since this seems to only be for a warning diagnostic, I skipped
the diagnostic check if it returned null. But mabye there's a
different way to fix this.
2023-03-16 21:37:35 -07:00
.github workflows: Don't try and run llvm-bugs in forks 2023-03-16 16:47:07 +00:00
bolt Use *{Map,Set}::contains (NFC) 2023-03-15 22:55:35 -07:00
clang Recommit "[Sema] Fix null pointer dereference handleAlwaysInlineAttr." 2023-03-16 21:37:35 -07:00
clang-tools-extra [clang] Fix a UsingTemplate regression after 3e78fa8602 2023-03-16 12:59:26 +01:00
cmake Revert "[CMake] Unify llvm_check_linker_flag and llvm_check_compiler_linker_flag" 2023-03-12 13:27:23 +07:00
compiler-rt Revert "[LSAN][HWASAN] Turn on leak sanitizer in HWASAN for Linux" 2023-03-16 19:16:16 -07:00
cross-project-tests [Dexter] Add a simple logging class to Dexter 2023-03-15 19:25:37 +00:00
flang [flang] Make tests depend on llvm-readobj not llvm-readelf 2023-03-16 16:39:22 +00:00
libc [libc][Obvious] Reduce the size of the tests for hypot(f). 2023-03-16 21:17:20 -04:00
libclc Revert "[CMake] Bumps minimum version to 3.20.0." 2023-03-04 18:28:13 +01:00
libcxx [libcxx] Add status paper for Parallelism-TS 2023-03-17 12:31:32 +08:00
libcxxabi [runtimes] Synchronize warnings flags between libc++/libc++abi/libunwind 2023-03-17 00:40:59 +01:00
libunwind [runtimes] Synchronize warnings flags between libc++/libc++abi/libunwind 2023-03-17 00:40:59 +01:00
lld [wasm] Silence 'not all control paths return a value' warning when 2023-03-15 14:20:18 -04:00
lldb Remove #if guards from AppendBounds to fix compile on old POSIX. 2023-03-16 16:16:21 -07:00
llvm [X86] Remove unreachable code in X86TargetTransformInfo.cpp 2023-03-17 00:33:06 -04:00
llvm-libgcc Revert "[CMake] Bumps minimum version to 3.20.0." 2023-03-04 18:28:13 +01:00
mlir [mlir][transform] change RaggedArray internals 2023-03-16 23:13:53 +00:00
openmp [OpenMP][libomptarget][AMDGPU] Update print launch info 2023-03-15 06:11:01 -04:00
polly Use *{Map,Set}::contains (NFC) 2023-03-15 22:55:35 -07:00
pstl Revert "[CMake] Bumps minimum version to 3.20.0." 2023-03-04 18:28:13 +01:00
runtimes [runtimes] Synchronize warnings flags between libc++/libc++abi/libunwind 2023-03-17 00:40:59 +01:00
third-party Remove an extra // in the IWYU pragma for gtest-matchers.h 2023-03-14 13:11:53 +01:00
utils [llvm][Bazel] Include .inc files in tblgen target. 2023-03-16 13:32:37 +01:00
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore
.mailmap
CONTRIBUTING.md
LICENSE.TXT
README.md [docs] Update README and GettingStarted 2023-03-08 12:55:59 -08:00
SECURITY.md

The LLVM Compiler Infrastructure

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.

Getting the Source Code and Building LLVM

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.

Getting in touch

Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.