summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2018-04-17 11:08:05 +0000
committerChandler Carruth <chandlerc@gmail.com>2018-04-17 11:08:05 +0000
commit6a4a524146226e98be04697d57a574f743052323 (patch)
tree87420f2ccd460ab11ca152da10c0bfa06a36be01 /clang/lib/Frontend/CompilerInvocation.cpp
parente256ab847b7621f67e3d24a62e72d493ab7b6d32 (diff)
downloadbcm5719-llvm-6a4a524146226e98be04697d57a574f743052323.tar.gz
bcm5719-llvm-6a4a524146226e98be04697d57a574f743052323.zip
Add some infuriatingly necessary comments to this test case.
Without these comments, by "luck" the contents of SomeKit's SKWidget.h are precisely the same as SomeKitCore's SomeKitCore.h. This can create havoc if anything canonicalizes on the inode and your filesystem assigns a common inode to files with identical file content. Alternatively, if your build system uses symlinks into a content-addressed-storage (as Google's does), you end up with these files being symlinks to the same file. The end result is that Clang deduplicates them internally, and then believes that the SomeKit framework includes the SomeKitCore.h header, and does not include the SKWidget.h in SomeKit. This in turn results in warnings in this test and eventually errors as Clang becomes confused because the umbrella header for SomeKitCore has already been included into another framework's module (SomeKit). Yay. If anyone has a better idea about how to avoid this, I'm all ears. Nothing other than causing the file content to change worked for me. llvm-svn: 330184
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud