llvm-project/clang
Manman Ren 33d8029589 PCH + module: make sure we write out macros associated with builtin identifiers.
When we import a module that defines a builtin identifier from prefix header and
precompile the prefix header, the macro information related to the identifier
is lost.

If we don't precompile the prefix header, the source file can still see the
macro information. The reason is that we write out the identifier in the pch
but not the macro information since the macro is not defined locally.

This is related to r251565. In that commit, if we read a builtin identifier from
a module that wasn't "interesting" to that module, we will still write it out to
a PCH that imports that module.

The fix is to write exported module macros for PCH as well.

rdar://24666630

Differential Revision: http://reviews.llvm.org/D20383

llvm-svn: 271310
2016-05-31 18:19:32 +00:00
..
INPUTS
bindings Enable support for __float128 in Clang and enable it on pertinent platforms 2016-05-09 08:52:33 +00:00
cmake [cmake] Enable zlib support for Apple stage2 builds 2016-05-09 18:40:09 +00:00
docs [ASTMatchers] Breaking change of `has` matcher 2016-05-31 15:25:05 +00:00
examples AnnotateFunctions: Tweak for mingw. 2016-04-04 15:30:44 +00:00
include Fixed bug 2016-05-31 15:56:26 +00:00
lib PCH + module: make sure we write out macros associated with builtin identifiers. 2016-05-31 18:19:32 +00:00
runtime [CMake] Pass LLVM_LIBDIR_SUFFIX into Compiler-RT 2016-05-10 16:10:22 +00:00
test PCH + module: make sure we write out macros associated with builtin identifiers. 2016-05-31 18:19:32 +00:00
tools clang-c: Add the clang_getCursorVisibility() API 2016-05-31 15:55:51 +00:00
unittests [ASTMatchers] Breaking change of `has` matcher 2016-05-31 15:25:05 +00:00
utils Work around MinGW's macro definition of 'interface' to 'struct' 2016-05-31 17:42:56 +00:00
www [www][analyzer] Update recommended suppression mechanism for localization. 2016-05-06 18:13:30 +00:00
.arcconfig
.clang-format
.clang-tidy Try to use readability-identifier-naming check on Clang. 2016-04-13 08:59:49 +00:00
.gitignore Add the clang debug info test directory to .gitignore as it's managed separately. 2016-01-29 01:35:55 +00:00
CMakeLists.txt [CMake] On Darwin bootstrap LTO builds set DYLD_LIBRARY_PATH instead of using llvm-ar 2016-04-27 18:52:48 +00:00
CODE_OWNERS.TXT Added Anastasia Stulova as a code owner for OpenCL 2016-02-03 18:51:19 +00:00
INSTALL.txt Honor system specific paths of MAN pages 2015-11-20 18:49:02 +00:00
LICENSE.TXT Update copyright year to 2016. 2016-03-30 22:38:44 +00:00
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/