summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Object/MachOObject.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2011-11-05 10:15:33 +0000
committerChandler Carruth <chandlerc@gmail.com>2011-11-05 10:15:33 +0000
commit979272c01c1b00f8c3ae6355e39298969aecbd3b (patch)
treef3b1b42ea1ad2fc4435c2ce3401aee148ad76d9d /llvm/lib/Object/MachOObject.cpp
parente3fcb6981f05620f8b29933c9f1d3bd4f08a3ece (diff)
downloadbcm5719-llvm-979272c01c1b00f8c3ae6355e39298969aecbd3b.tar.gz
bcm5719-llvm-979272c01c1b00f8c3ae6355e39298969aecbd3b.zip
Change this test to reflect the state we are moving in. The Clang
builtin headers are no longer going to receive the old 'implicit extern "C" block' semantics. This hint is actually ignored by both Clang and GCC at this point, and Clang's own builtin headers can simply be changed if there is any issue with this. Clang should be free to include these however it wants, and so shorter and simpler is better. Note: *nothing* is changing about the *system* stddef.h include. That should always have the exact same include semantics, whether with Clang or GCC or any other compiler. Only the compiler-builtin header search path is changing. If anyone knows of some risk that this introduces that I've not thought of, please chime in. So far, only Windows has switched to the Brave New World, but others should be switching soon. llvm-svn: 143806
Diffstat (limited to 'llvm/lib/Object/MachOObject.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud