llvm-project

History

Ben Dunbobbin ae9231ca2a Reland - [Clang] Add the ability to map DLL storage class to visibility `415f7ee883` had LIT test failures on any build where the clang executable was not called "clang". I have adjusted the LIT CHECKs to remove the binary name to fix this. Original commit message: For PlayStation we offer source code compatibility with Microsoft's dllimport/export annotations; however, our file format is based on ELF. To support this we translate from DLL storage class to ELF visibility at the end of codegen in Clang. Other toolchains have used similar strategies (e.g. see the documentation for this ARM toolchain: https://developer.arm.com/documentation/dui0530/i/migrating-from-rvct-v3-1-to-rvct-v4-0/changes-to-symbol-visibility-between-rvct-v3-1-and-rvct-v4-0) This patch adds the ability to perform this translation. Options are provided to support customizing the mapping behaviour. Differential Revision: https://reviews.llvm.org/D89970		2020-11-02 23:24:49 +00:00
..
INPUTS	…
bindings	[NFC] Don't run python binding tests with sanitizers	2020-10-29 23:48:08 -07:00
cmake	Added remotely ran compiler-rt tests.	2020-10-30 00:11:16 +04:00
docs	Add option 'exceptions' to pragma clang fp	2020-10-31 17:36:12 +07:00
examples	Correct examples after `d3205bbca3`	2020-10-27 09:49:33 +01:00
include	Reland - [Clang] Add the ability to map DLL storage class to visibility	2020-11-02 23:24:49 +00:00
lib	Reland - [Clang] Add the ability to map DLL storage class to visibility	2020-11-02 23:24:49 +00:00
runtime	[CMake][compiler-rt][libunwind] Compile assembly files as ASM not C, unify workarounds	2020-08-27 15:40:15 +03:00
test	Reland - [Clang] Add the ability to map DLL storage class to visibility	2020-11-02 23:24:49 +00:00
tools	Change Module::ASTFile and ModuleFile::File => Optional<FileEntryRef>, NFC	2020-11-02 15:11:51 -05:00
unittests	Ignore template instantiations if not in AsIs mode	2020-11-02 20:21:48 +00:00
utils	[hmaptool] Fix `NameError: global name 'num_buckets' is not defined` in `action_dump`.	2020-10-19 16:27:13 -07:00
www	PR47954 / DR2126: permit temporary objects that are lifetime-extended by	2020-10-23 14:29:18 -07:00
.clang-format	…
.clang-tidy	…
.gitignore	…
CMakeLists.txt	[clang] Limit scope of CLANG_VENDOR definition	2020-11-02 09:04:43 -08:00
CODE_OWNERS.TXT	…
INSTALL.txt	…
LICENSE.TXT	…
ModuleInfo.txt	…
NOTES.txt	…
README.txt	…

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/