aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenFunction.h
diff options
context:
space:
mode:
authorMartin Storsjö <martin@martin.st>2021-12-08 20:54:21 +0200
committerMartin Storsjö <martin@martin.st>2021-12-22 15:16:58 +0200
commit7176799a7e196fa41046f9c77ebd65335b339acd (patch)
tree0a1dd40dd5050c4afd2e2350bd7969bd8ddb67f2 /clang/lib/CodeGen/CodeGenFunction.h
parentfd64544fbe0a4c0ed5d6d0cdda3945aacf7e9593 (diff)
downloadllvm-7176799a7e196fa41046f9c77ebd65335b339acd.zip
llvm-7176799a7e196fa41046f9c77ebd65335b339acd.tar.gz
llvm-7176799a7e196fa41046f9c77ebd65335b339acd.tar.bz2
[libc++] Add from-scratch testing configs for Windows
The paths to the compiler and to the python executable may need to be quoted (if they're installed into e.g. C:\Program Files). All testing commands that are executed expect a gcc compatible command line interface, while clang-cl uses different command line options. In the original testing config, if the chosen compiler was clang-cl, it was replaced with clang++ by looking for such an executable in the path. For the new from-scratch test configs, I instead chose to add "--driver-mode=g++" to flags - invoking "clang-cl --driver-mode=g++" has the same effect as invoking "clang++", without needing to run any heuristics for picking a different compiler executable. Differential Revision: https://reviews.llvm.org/D111202
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.h')
0 files changed, 0 insertions, 0 deletions