llvm-project/clang
Anastasia Stulova 257132a019 [OpenCL] Handle taking an address of block captures.
Block captures can have different physical locations
in memory segments depending on the use case (as a function
call or as a kernel enqueue) and in different vendor
implementations.

Therefore it's unclear how to add address space to capture
addresses uniformly. Currently it has been decided to disallow
taking addresses of captured variables until further
clarifications in the spec.

Differential Revision: https://reviews.llvm.org/D36410

llvm-svn: 312728
2017-09-07 17:00:33 +00:00
..
INPUTS
bindings Fix __repr__ for Diagnostic in clang.cindex 2017-09-06 07:33:32 +00:00
cmake Remove LLVMFuzzer from list of bundled libraries for Fuchsia 2017-08-23 00:09:33 +00:00
docs [clang-format] Fix documentation for AllowAllParametersOfDeclarationOnNextLine 2017-09-07 13:45:41 +00:00
examples Add LLVMOption to clang-interpreter, corresponding to r291938. 2017-01-14 08:54:05 +00:00
include [OpenCL] Handle taking an address of block captures. 2017-09-07 17:00:33 +00:00
lib [OpenCL] Handle taking an address of block captures. 2017-09-07 17:00:33 +00:00
runtime Enable check-ubsan-minimal in standalone compiler-rt build. 2017-09-01 20:37:20 +00:00
test [OpenCL] Handle taking an address of block captures. 2017-09-07 17:00:33 +00:00
tools [diagtool] Change default tree behavior to print only flags 2017-09-05 18:04:40 +00:00
unittests [clang-format] Add support for C++17 structured bindings. 2017-09-07 14:28:32 +00:00
utils [AST] Add TableGen for StmtDataCollectors 2017-09-06 13:20:51 +00:00
www P0702R1: in class template argument deduction from a list of one element, if 2017-09-07 07:22:36 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt Don't search libxml2 if using msan. LLVM already has similar check. 2017-09-02 03:53:42 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt Test commit access in clang. 2017-09-03 15:29:38 +00:00

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/