summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/LiveInterval.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2015-03-07 10:01:29 +0000
committerChandler Carruth <chandlerc@gmail.com>2015-03-07 10:01:29 +0000
commit7e7dd47fc21daf11c12484f4e9c4585b70d91560 (patch)
treeaefa290671bf891a6a74f97045da028926b8f6ce /llvm/lib/CodeGen/LiveInterval.cpp
parentdf397c520d48937df0a44bea3a49190176e107f2 (diff)
downloadbcm5719-llvm-7e7dd47fc21daf11c12484f4e9c4585b70d91560.tar.gz
bcm5719-llvm-7e7dd47fc21daf11c12484f4e9c4585b70d91560.zip
Much like we silence warnings about -flto in many cases to facilitate
simplicity in build systems, silence '-stdlib=libc++' when linking. Even if we're not linking C++ code per-se, we may be passing this flag so that when we are linking C++ code we pick up the desired standard library. While most build systems already provide separate C and C++ compile flags, many conflate link flags. Sadly, CMake is among them causing this warning in a libc++ selfhost. llvm-svn: 231559
Diffstat (limited to 'llvm/lib/CodeGen/LiveInterval.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud