summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/WebAssembly
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2018-08-27 21:53:36 +0000
committerZachary Turner <zturner@google.com>2018-08-27 21:53:36 +0000
commit522f9aec18bc15c920236e96a16c9984b4bc3a04 (patch)
tree40bb528ca04870a1ded365c6d5f7fde03baaff75 /llvm/lib/Target/WebAssembly
parentf05f93879b84d73c13a354e10b6c41d4cc3722a7 (diff)
downloadbcm5719-llvm-522f9aec18bc15c920236e96a16c9984b4bc3a04.tar.gz
bcm5719-llvm-522f9aec18bc15c920236e96a16c9984b4bc3a04.zip
Update the Visual Studio Integration from user feedback.
This patch removes the MSBuild warnings about options that clang-cl ignores. It also adds several additional fields to the LLVM Configuration options page. The first is that it adds support for LLD! To give the user flexibility though, we don't want to force LLD to always-on, and if we're not forcing LLD then we might as well not force clang-cl either. So we add options that can enable or disable lld, clang-cl, or any combination of the two. Whenever one is disabled, it falls back to the Microsoft equivalent. Additionally, for each of clang-cl and lld-link, we add a new configuration setting that allows Additional Options to be passed for that specific tool only. This is similar to the C/C++ > Command Line > Additional Options entry box, but it serves the use case where a user switches back and forth between the toolsets in their vcxproj, but where cl.exe won't accept some options that clang-cl will. In this case you can pass those options in the clang-cl additional options and whenever clang-cl is disabled (or the other toolset is selected entirely), those options won't get passed at all. llvm-svn: 340780
Diffstat (limited to 'llvm/lib/Target/WebAssembly')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud