llvm with tablegen backend for capstone disassembler
Go to file
bd1976bris cd05ade13a
Add a "don't override" mapping for -fvisibility-from-dllstorageclass (#74629)
`-fvisibility-from-dllstorageclass` allows for overriding the visibility
of globals from their DLL storage class. The visibility to apply can be
customised for the different classes of globals via a set of dependent
options that specify the mapping values:
- `-fvisibility-dllexport=<value>`
- `-fvisibility-nodllstorageclass=<value>`
- `-fvisibility-externs-dllimport=<value>`
- `-fvisibility-externs-nodllstorageclass=<value>` 

Currently, one of the existing LLVM visibilities, `hidden`, `protected`,
`default`, can be used as a mapping value. This change adds a new
mapping value: `keep`, which specifies that the visibility should not be
overridden for that class of globals. The behaviour of
`-fvisibility-from-dllstorageclass` is otherwise unchanged and existing
uses of this set of options will be unaffected.

The background to this change is that currently the PS4 and PS5
compilers effectively ignore visibility - dllimport/export is the
supported method for export control in C/C++ source code. Now, we would
like to support visibility attributes and options in our frontend, in
addition to dllimport/export. To support this, we will override the
visibility of globals with explicit dllimport/export annotations but use
the `keep` setting for globals which do not have an explicit
dllimport/export.

There are also some minor improvements to the existing options:
- Make the `LANGOPS` `BENIGN` as they don't involve the AST.
- Correct/clarify the help text for the options.
2024-01-19 21:57:40 +00:00
.ci [CI] Add lld as compiler-rt dependecy (#78536) 2024-01-17 21:10:54 -08:00
.github Revert #76246 and #76083 2024-01-18 15:07:33 -08:00
bolt [BOLT] Fix unconditional output of boltedcollection in merge-fdata (#78653) 2024-01-18 20:00:47 -08:00
clang Add a "don't override" mapping for -fvisibility-from-dllstorageclass (#74629) 2024-01-19 21:57:40 +00:00
clang-tools-extra [clang-apply-replacements] Deduplicate Implementation of collectReplacementsFromDirectory (NFC) (#78630) 2024-01-19 15:57:02 +03:00
cmake [CMake] Switch the CMP0091 policy (MSVC_RUNTIME_LIBRARY) to the new behaviour 2023-07-17 09:59:05 +03:00
compiler-rt Re-exec TSan with no ASLR if memory layout is incompatible on Linux (#78351) 2024-01-19 09:33:54 -08:00
cross-project-tests Revert "[BOLT] Fix unconditional output of boltedcollection in merge-fdata (#78653)" 2024-01-18 19:59:09 -08:00
flang [Flang][OpenMP] Consider renames when processing reduction intrinsics (#70822) 2024-01-19 15:17:21 +00:00
libc [libc] remove extra -Werror (#78761) 2024-01-19 12:28:06 -08:00
libclc libclc: generic: add half implementation for erf/erfc (#66901) 2024-01-09 16:47:53 +00:00
libcxx [libc++][hardening] In production hardening modes, trap rather than abort (#78561) 2024-01-19 13:48:13 -08:00
libcxxabi [libc++abi] Fix typo in CMake error message 2024-01-16 10:56:03 -05:00
libunwind [libunwind] Move errno.h and signal.h includes under the block where they're needed (#78054) 2024-01-16 10:31:01 -05:00
lld [lld][WebAssembly] Reset context object after each link (#78770) 2024-01-19 13:51:35 -08:00
lldb [lldb][test] Apply @expectedFailureAll/@skipIf early for debug_info tests (#73067) 2024-01-19 10:50:05 -06:00
llvm [Statepoint][NFC] Use uint16_t and add an assert (#78717) 2024-01-20 00:44:00 +03:00
llvm-libgcc [llvm-libgcc][CMake] Refactor llvm-libgcc (#65455) 2023-09-18 22:56:03 -07:00
mlir [mlir][transform] Add an op for replacing values with function calls (#78398) 2024-01-19 13:21:52 -05:00
openmp [openmp] Revert 64874e5ab5 since it was committed by mistake and the PR (https://github.com/llvm/llvm-project/pull/77853) wasn't approved yet. 2024-01-18 13:55:03 -05:00
polly [AST] Don't merge memory locations in AliasSetTracker (#65731) 2024-01-17 15:59:13 +01:00
pstl Clear release notes for 18.x 2023-07-25 13:58:49 +02:00
runtimes [CMake] Always define runtimes-test-depends (#73629) 2023-11-28 15:30:52 -08:00
third-party [third-party] Silence warning on benchmark when building with Clang ToT 2024-01-17 07:23:56 -05:00
utils [mlir][transform]: fix broken bazel build for TensorTransformOps (#78766) 2024-01-19 20:33:36 +01:00
.arcconfig
.arclint
.clang-format
.clang-tidy Add -misc-use-anonymous-namespace to .clang-tidy 2023-05-06 02:33:20 +03:00
.git-blame-ignore-revs [libc++] Add libc++ clang-formatting commit to git-blame-ignore-revs file 2023-12-18 14:04:41 -05:00
.gitattributes [libc++] Format the code base (#74334) 2023-12-18 14:01:33 -05:00
.gitignore Revert accidental .gitignore change from 9b7763821a 2023-09-07 22:42:05 -07:00
.mailmap .mailmap: add second entry for self 2023-12-19 11:13:19 +00:00
CODE_OF_CONDUCT.md [llvm] Add CODE_OF_CONDUCT.md (#65816) 2023-09-09 10:55:31 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md to remove the not about not accepting PR 2023-09-10 15:21:06 -07:00
LICENSE.TXT [docs] Add LICENSE.txt to the root of the mono-repo 2022-08-24 09:35:00 +02:00
README.md Add OpenSSF Best Practice Badge (#77398) 2024-01-13 07:43:11 -08:00
SECURITY.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

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, 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.