maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Driver/cl-options.c

676 lines
26 KiB
C
Raw Normal View History

Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Note: %s must be preceded by --, otherwise it may be interpreted as a
// command-line option, e.g. on Mac where %s is commonly under /Users.
clang-cl: add the /c, /W0 and /W1 options This adds a few more clang-cl options. It also exposes two core clang options to the clang-cl mode: we need to be able to claim --driver_mode so it doesn't show up as unused in cl mode, and we need -### for tests. Differential Revision: http://llvm-reviews.chandlerc.com/D1232 llvm-svn: 187527
2013-08-01 04:51:53 +08:00
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Alias options:
clang-cl: accept the /C option with /P (PR19978) (It's also allowed with /EP, but we haven't implemented that option yet.) llvm-svn: 210695
2014-06-12 03:44:53 +08:00
// RUN: %clang_cl /c -### -- %s 2>&1 | FileCheck -check-prefix=c %s
// c: -c
// RUN: %clang_cl /C -### -- %s 2>&1 | FileCheck -check-prefix=C %s
Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics With this, `clang-cl /source-charset:utf-16 test.cc` now prints `invalid value 'utf-16' in '/source-charset:utf-16'` instead of `invalid value 'utf-16' in '-finput-charset=utf-16'` before, and several other clang-cl flags produce much less confusing output as well. Fixes PR29106. Since an arg and its alias can have different arg types (joined vs not) and different values (because of AliasArgs<>), I chose to give the Alias its own Arg object. For convenience, I just store the alias directly in the unaliased arg – there aren't many arg objects at runtime, so that seems ok. Finally, I changed Arg::getAsString() to use the alias's representation if it's present – that function was already documented as being the suitable function for diagnostics, and most callers already used it for diagnostics. Implementation-wise, Arg::accept() previously used to parse things as the unaliased option. The core of that switch is now extracted into a new function acceptInternal() which parses as the _aliased_ option, and the previously-intermingled unaliasing is now done as an explicit step afterwards. (This also changes one place in lld that didn't use getAsString() for diagnostics, so that that one place now also prints the flag as the user wrote it, not as it looks after it went through unaliasing.) Differential Revision: https://reviews.llvm.org/D64253 llvm-svn: 365413
2019-07-09 08:34:08 +08:00
// C: error: invalid argument '/C' only allowed with '/E, /P or /EP'
clang-cl: accept the /C option with /P (PR19978) (It's also allowed with /EP, but we haven't implemented that option yet.) llvm-svn: 210695
2014-06-12 03:44:53 +08:00
// RUN: %clang_cl /C /P -### -- %s 2>&1 | FileCheck -check-prefix=C_P %s
// C_P: "-E"
// C_P: "-C"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Make /d1reportAllClassLayout actually work and improve test See review thread for r301567. llvm-svn: 364901
2019-07-02 18:22:11 +08:00
// RUN: %clang_cl /d1reportAllClassLayout -### /c /WX -- %s 2>&1 | \
// RUN: FileCheck -check-prefix=d1reportAllClassLayout %s
// d1reportAllClassLayout-NOT: warning:
// d1reportAllClassLayout-NOT: error:
clang-cl: Alias /d1reportAllClassLayout to -fdump-record-layouts (PR32826) llvm-svn: 301567
2017-04-28 01:19:07 +08:00
// d1reportAllClassLayout: -fdump-record-layouts
Follow-up to r257537: add test that majnemer asked about llvm-svn: 257541
2016-01-13 07:31:58 +08:00
// RUN: %clang_cl /Dfoo=bar /D bar=baz /DMYDEF#value /DMYDEF2=foo#bar /DMYDEF3#a=b /DMYDEF4# \
clang-cl: Support /Dfoo#bar (PR25984) Such flags will now be translated to -Dfoo=bar. llvm-svn: 257537
2016-01-13 07:17:03 +08:00
// RUN: -### -- %s 2>&1 | FileCheck -check-prefix=D %s
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// D: "-D" "foo=bar"
clang-cl: Support /Dfoo#bar (PR25984) Such flags will now be translated to -Dfoo=bar. llvm-svn: 257537
2016-01-13 07:17:03 +08:00
// D: "-D" "bar=baz"
// D: "-D" "MYDEF=value"
// D: "-D" "MYDEF2=foo#bar"
// D: "-D" "MYDEF3=a=b"
Follow-up to r257537: add test that majnemer asked about llvm-svn: 257541
2016-01-13 07:31:58 +08:00
// D: "-D" "MYDEF4="
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Support /P and /E (preprocess to file or stdout) llvm-svn: 197827
2013-12-21 02:40:46 +08:00
// RUN: %clang_cl /E -### -- %s 2>&1 | FileCheck -check-prefix=E %s
// E: "-E"
// E: "-o" "-"
Add support for the /EP argument to clang-cl This maps the /EP argument to both -E and -P. Patch by Ehsan Akhgari! Differential Reviion: http://reviews.llvm.org/D4133 llvm-svn: 210935
2014-06-14 04:59:54 +08:00
// RUN: %clang_cl /EP -### -- %s 2>&1 | FileCheck -check-prefix=EP %s
// EP: "-E"
// EP: "-P"
// EP: "-o" "-"
clang-cl: Support the /fp options (PR23112) This hooks up the /fp options as aliases for -f[no-]fast-math and -f[no]-trapping-math. It probably doesn't match cl.exe's behaviour completely (e.g. LLVM is currently never as precise as /fp:precise), but it's close enough. Differential revision: http://reviews.llvm.org/D8909 llvm-svn: 234449
2015-04-09 06:55:09 +08:00
// RUN: %clang_cl /fp:fast /fp:except -### -- %s 2>&1 | FileCheck -check-prefix=fpexcept %s
// fpexcept-NOT: -menable-unsafe-fp-math
// RUN: %clang_cl /fp:fast /fp:except /fp:except- -### -- %s 2>&1 | FileCheck -check-prefix=fpexcept_ %s
// fpexcept_: -menable-unsafe-fp-math
// RUN: %clang_cl /fp:precise /fp:fast -### -- %s 2>&1 | FileCheck -check-prefix=fpfast %s
// fpfast: -menable-unsafe-fp-math
// fpfast: -ffast-math
// RUN: %clang_cl /fp:fast /fp:precise -### -- %s 2>&1 | FileCheck -check-prefix=fpprecise %s
// fpprecise-NOT: -menable-unsafe-fp-math
// fpprecise-NOT: -ffast-math
// RUN: %clang_cl /fp:fast /fp:strict -### -- %s 2>&1 | FileCheck -check-prefix=fpstrict %s
// fpstrict-NOT: -menable-unsafe-fp-math
// fpstrict-NOT: -ffast-math
Omit column info for CodeView by default Clang tracks only start columns, not start-end ranges. CodeView allows for that, but the VS debugger doesn't handle anything less than a complete range well--it either highlights the wrong part of a statement or truncates source lines in the assembly view. It's better to have no column information at all. So by default, we'll omit the column information for CodeView targeting Windows. Since the column info is still useful for sanitizers, I've promoted -gcolumn-info (and -gno-column-info) to a CoreOption and added a couple tests to make sure that works for clang-cl. Differential Revision: https://reviews.llvm.org/D23720 llvm-svn: 279765
2016-08-26 02:24:35 +08:00
// RUN: %clang_cl /Z7 -gcolumn-info -### -- %s 2>&1 | FileCheck -check-prefix=gcolumn %s
// gcolumn: -dwarf-column-info
// RUN: %clang_cl /Z7 -gno-column-info -### -- %s 2>&1 | FileCheck -check-prefix=gnocolumn %s
// gnocolumn-NOT: -dwarf-column-info
// RUN: %clang_cl /Z7 -### -- %s 2>&1 | FileCheck -check-prefix=gdefcolumn %s
// gdefcolumn-NOT: -dwarf-column-info
[Driver][Windows] Add dependent lib argument for -fprofile-generate and -fcs-profile-generate Follows on from r360674 which added it for -fprofile-instr-generate. Differential Revision: https://reviews.llvm.org/D62200 llvm-svn: 361368
2019-05-22 18:06:49 +08:00
// RUN: %clang_cl -### /FA -fprofile-instr-generate -- %s 2>&1 | FileCheck -check-prefix=CHECK-PROFILE-INSTR-GENERATE %s
// RUN: %clang_cl -### /FA -fprofile-instr-generate=/tmp/somefile.profraw -- %s 2>&1 | FileCheck -check-prefix=CHECK-PROFILE-INSTR-GENERATE-FILE %s
// CHECK-PROFILE-INSTR-GENERATE: "-fprofile-instrument=clang" "--dependent-lib={{[^"]*}}clang_rt.profile-{{[^"]*}}.lib"
// CHECK-PROFILE-INSTR-GENERATE-FILE: "-fprofile-instrument-path=/tmp/somefile.profraw"
// RUN: %clang_cl -### /FA -fprofile-generate -- %s 2>&1 | FileCheck -check-prefix=CHECK-PROFILE-GENERATE %s
// CHECK-PROFILE-GENERATE: "-fprofile-instrument=llvm" "--dependent-lib={{[^"]*}}clang_rt.profile-{{[^"]*}}.lib"
make -fprofile-instr-generate and -fprofile-instr-use work with clang-cl Summary: Makes -fprofile-instr-generate and -fprofile-instr-use work with clang-cl so that profile-guided optimization can be used. Differential Revision: https://reviews.llvm.org/D27086 llvm-svn: 288230
2016-11-30 11:25:36 +08:00
// RUN: %clang_cl -### /FA -fprofile-instr-generate -fprofile-instr-use -- %s 2>&1 | FileCheck -check-prefix=CHECK-NO-MIX-GEN-USE %s
// RUN: %clang_cl -### /FA -fprofile-instr-generate -fprofile-instr-use=file -- %s 2>&1 | FileCheck -check-prefix=CHECK-NO-MIX-GEN-USE %s
// CHECK-NO-MIX-GEN-USE: '{{[a-z=-]*}}' not allowed with '{{[a-z=-]*}}'
// RUN: %clang_cl -### /FA -fprofile-instr-use -- %s 2>&1 | FileCheck -check-prefix=CHECK-PROFILE-USE %s
// RUN: %clang_cl -### /FA -fprofile-instr-use=/tmp/somefile.prof -- %s 2>&1 | FileCheck -check-prefix=CHECK-PROFILE-USE-FILE %s
// CHECK-PROFILE-USE: "-fprofile-instrument-use-path=default.profdata"
// CHECK-PROFILE-USE-FILE: "-fprofile-instrument-use-path=/tmp/somefile.prof"
[clang-cl] Map /GA to -ftls-model=local-exec The /GA switch informs the compiler that it may assume that all TLS access refers to the executable's index: 0. llvm-svn: 237771
2015-05-20 12:39:56 +08:00
// RUN: %clang_cl /GA -### -- %s 2>&1 | FileCheck -check-prefix=GA %s
// GA: -ftls-model=local-exec
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RTTI is on by default; just check that we don't error.
// RUN: %clang_cl /Zs /GR -- %s 2>&1
// RUN: %clang_cl /GR- -### -- %s 2>&1 | FileCheck -check-prefix=GR_ %s
// GR_: -fno-rtti
Add support to clang-cl driver for /GS switch Summary: This patch is adding command-line support for the MSVC buffer security check. The buffer security check is turned on with the '/GS' compiler switch. https://msdn.microsoft.com/en-us/library/8dbf701c.aspx The MSVC buffer security check in implemented here: http://reviews.llvm.org/D20346 Reviewers: hans, rnk Subscribers: chrisha, cfe-commits, rnk, hans, thakis Differential Revision: http://reviews.llvm.org/D20347 llvm-svn: 272832
2016-06-16 04:34:33 +08:00
// Security Buffer Check is on by default.
// RUN: %clang_cl -### -- %s 2>&1 | FileCheck -check-prefix=GS-default %s
// GS-default: "-stack-protector" "2"
// RUN: %clang_cl /GS -### -- %s 2>&1 | FileCheck -check-prefix=GS %s
// GS: "-stack-protector" "2"
// RUN: %clang_cl /GS- -### -- %s 2>&1 | FileCheck -check-prefix=GS_ %s
// GS_-NOT: -stack-protector
Driver: Map /Gy to -ffunction-sections /Gy is equivalent to -ffunction-sections. /Gy- is equivalent to -fno-function-sections. Currently, LLVM doesn't do anything interesting with -ffunction-sections under WinCOFF. llvm-svn: 204564
2014-03-24 01:47:22 +08:00
// RUN: %clang_cl /Gy -### -- %s 2>&1 | FileCheck -check-prefix=Gy %s
// Gy: -ffunction-sections
// RUN: %clang_cl /Gy /Gy- -### -- %s 2>&1 | FileCheck -check-prefix=Gy_ %s
// Gy_-NOT: -ffunction-sections
Implement command line options for stack probe space This code adds the -mstack-probe-size command line option and implements the /Gs compiler switch for clang-cl. This should fix http://llvm.org/bugs/show_bug.cgi?id=21896 Patch by Andrew H! Differential Revision: http://reviews.llvm.org/D6685 llvm-svn: 226601
2015-01-21 03:45:50 +08:00
// RUN: %clang_cl /Gs -### -- %s 2>&1 | FileCheck -check-prefix=Gs %s
[clang-cl] Make /Gs imply default stack probes, not /Gs0 (PR39074) Differential revision: https://reviews.llvm.org/D52499 llvm-svn: 343077
2018-09-26 15:39:04 +08:00
// Gs: "-mstack-probe-size=4096"
Implement command line options for stack probe space This code adds the -mstack-probe-size command line option and implements the /Gs compiler switch for clang-cl. This should fix http://llvm.org/bugs/show_bug.cgi?id=21896 Patch by Andrew H! Differential Revision: http://reviews.llvm.org/D6685 llvm-svn: 226601
2015-01-21 03:45:50 +08:00
// RUN: %clang_cl /Gs0 -### -- %s 2>&1 | FileCheck -check-prefix=Gs0 %s
// Gs0: "-mstack-probe-size=0"
// RUN: %clang_cl /Gs4096 -### -- %s 2>&1 | FileCheck -check-prefix=Gs4096 %s
// Gs4096: "-mstack-probe-size=4096"
clang-cl: make /Gw map to -fdata-sections Note that /Gy no longer implies -fdata-sections. llvm-svn: 205716
2014-04-08 00:14:38 +08:00
// RUN: %clang_cl /Gw -### -- %s 2>&1 | FileCheck -check-prefix=Gw %s
// Gw: -fdata-sections
// RUN: %clang_cl /Gw /Gw- -### -- %s 2>&1 | FileCheck -check-prefix=Gw_ %s
// Gw_-NOT: -fdata-sections
clang-cl: Add /FI (forced include) as an alias for -include Patch by Jeff Muizelaar, with added test case. llvm-svn: 191442
2013-09-27 01:41:14 +08:00
// RUN: %clang_cl /Imyincludedir -### -- %s 2>&1 | FileCheck -check-prefix=SLASH_I %s
// RUN: %clang_cl /I myincludedir -### -- %s 2>&1 | FileCheck -check-prefix=SLASH_I %s
// SLASH_I: "-I" "myincludedir"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Remove -isystem, add -imsvc. r260990 exposed -isystem in clang-cl. -isystem adds a directory to the front of the system include search path. The idea was to use this to point to a hermetic msvc install, but as it turns out this doesn't work: -isystem then adds the hermetic headers in front of clang's builtin headers, and clang's headers that are supposed to wrap msvc headers (say, stdarg.h) aren't picked up at all anymore. So revert that, and instead expose -imsvc which works as if the passed directory was part of %INCLUDE%: The header is treated as a system header, but it is searched after clang's lib/Header headers. Fixes half of PRPR26751. llvm-svn: 266108
2016-04-13 03:04:37 +08:00
// RUN: %clang_cl /imsvcmyincludedir -### -- %s 2>&1 | FileCheck -check-prefix=SLASH_imsvc %s
// RUN: %clang_cl /imsvc myincludedir -### -- %s 2>&1 | FileCheck -check-prefix=SLASH_imsvc %s
// Clang's resource header directory should be first:
Fix testcase for the LLVM_LIBDIR_SUFFIX=64 case. Fallout from r266108. llvm-svn: 266324
2016-04-14 23:32:24 +08:00
// SLASH_imsvc: "-internal-isystem" "{{[^"]*}}lib{{(64)?/|\\\\}}clang{{[^"]*}}include"
clang-cl: Remove -isystem, add -imsvc. r260990 exposed -isystem in clang-cl. -isystem adds a directory to the front of the system include search path. The idea was to use this to point to a hermetic msvc install, but as it turns out this doesn't work: -isystem then adds the hermetic headers in front of clang's builtin headers, and clang's headers that are supposed to wrap msvc headers (say, stdarg.h) aren't picked up at all anymore. So revert that, and instead expose -imsvc which works as if the passed directory was part of %INCLUDE%: The header is treated as a system header, but it is searched after clang's lib/Header headers. Fixes half of PRPR26751. llvm-svn: 266108
2016-04-13 03:04:37 +08:00
// SLASH_imsvc: "-internal-isystem" "myincludedir"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /J -### -- %s 2>&1 | FileCheck -check-prefix=J %s
// J: -fno-signed-char
// RUN: %clang_cl /Ofoo -### -- %s 2>&1 | FileCheck -check-prefix=O %s
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// O: /Ofoo
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /Ob0 -### -- %s 2>&1 | FileCheck -check-prefix=Ob0 %s
// Ob0: -fno-inline
[Driver] Add support for -finline-functions and /Ob2 flags -finline-functions and /Ob2 are currently ignored by Clang. The only way to enable inlining is to use the global O flags, which also enable other options, or to emit LLVM bitcode using Clang, then running opt by hand with the inline pass. This patch allows to simply use the -finline-functions flag (same as GCC) or /Ob2 in clang-cl mode to enable inlining without other optimizations. This is the first patch of a serie to improve support for the /Ob flags. Patch by Rudy Pons <rudy.pons@ilod.org>! Differential Revision: http://reviews.llvm.org/D20576 llvm-svn: 270609
2016-05-25 04:40:51 +08:00
// RUN: %clang_cl /Ob2 -### -- %s 2>&1 | FileCheck -check-prefix=Ob2 %s
clang-cl: Bake /Ob0 and /Ob2 into the general /O option handling This is a follow-up to r270609, wherein I forgot that /O options can be combined, and e.g. /Odb2 is a valid combination. llvm-svn: 270614
2016-05-25 05:23:29 +08:00
// RUN: %clang_cl /Odb2 -### -- %s 2>&1 | FileCheck -check-prefix=Ob2 %s
clang-cl: Fix unused argument warning when combining /O2 and /Ob2 llvm-svn: 270642
2016-05-25 08:43:45 +08:00
// RUN: %clang_cl /O2 /Ob2 -### -- %s 2>&1 | FileCheck -check-prefix=Ob2 %s
// Ob2-NOT: warning: argument unused during compilation: '/O2'
[Driver] Add support for -finline-functions and /Ob2 flags -finline-functions and /Ob2 are currently ignored by Clang. The only way to enable inlining is to use the global O flags, which also enable other options, or to emit LLVM bitcode using Clang, then running opt by hand with the inline pass. This patch allows to simply use the -finline-functions flag (same as GCC) or /Ob2 in clang-cl mode to enable inlining without other optimizations. This is the first patch of a serie to improve support for the /Ob flags. Patch by Rudy Pons <rudy.pons@ilod.org>! Differential Revision: http://reviews.llvm.org/D20576 llvm-svn: 270609
2016-05-25 04:40:51 +08:00
// Ob2: -finline-functions
Add support for /Ob1 and -finline-hint-functions flags Add support for /Ob1 (and equivalent -finline-hint-functions), which enable inlining only for functions marked inline, either explicitly (via inline keyword, for example), or implicitly (function definition in class body, for example). This works by enabling inlining pass, and adding noinline attribute to every function not marked inline. Patch by Rudy Pons <rudy.pons@ilod.org>! Differential Revision: http://reviews.llvm.org/D20647 llvm-svn: 273440
2016-06-23 00:56:16 +08:00
// RUN: %clang_cl /Ob1 -### -- %s 2>&1 | FileCheck -check-prefix=Ob1 %s
// RUN: %clang_cl /Odb1 -### -- %s 2>&1 | FileCheck -check-prefix=Ob1 %s
// Ob1: -finline-hint-functions
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /Od -### -- %s 2>&1 | FileCheck -check-prefix=Od %s
// Od: -O0
clang-cl: Map /Oi[-] to -f[no-]builtin Differential Revision: http://llvm-reviews.chandlerc.com/D1328 llvm-svn: 188027
2013-08-09 07:44:01 +08:00
// RUN: %clang_cl /Oi- /Oi -### -- %s 2>&1 | FileCheck -check-prefix=Oi %s
// Oi-NOT: -fno-builtin
// RUN: %clang_cl /Oi- -### -- %s 2>&1 | FileCheck -check-prefix=Oi_ %s
// Oi_: -fno-builtin
fix previous commit Forgot to add the '='. In cl mode, --target must have an '='. llvm-svn: 249232
2015-10-03 15:15:28 +08:00
// RUN: %clang_cl /Os --target=i686-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Os %s
// RUN: %clang_cl /Os --target=x86_64-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Os %s
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// Os-NOT: -mdisable-fp-elim
[Driver] Refactor interaction between -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-frame-pointer Use a tri-state enum to represent shouldUseFramePointer() and shouldUseLeafFramePointer(). This simplifies the logic and fixes PR9825: -fno-omit-frame-pointer doesn't imply -mno-omit-leaf-frame-pointer. and PR24003: /Oy- /O2 should not omit leaf frame pointer: this matches MSVC x86-32. (/Oy- is a no-op on MSVC x86-64.) and: when CC1 option -mdisable-fp-elim if absent, -momit-leaf-frame-pointer can also be omitted. The new behavior matches GCC: -fomit-frame-pointer wins over -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer loses out to -momit-leaf-frame-pointer The behavior makes lots of sense. We have 4 states: - 00) leaf retained, non-leaf retained - 01) leaf retained, non-leaf omitted (this is invalid) - 10) leaf omitted, non-leaf retained (what -momit-leaf-frame-pointer was designed for) - 11) leaf omitted, non-leaf omitted "omit" options taking precedence over "no-omit" options is the only way to make 3 valid states representable with -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-pointer. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D64294 llvm-svn: 365860
2019-07-12 10:01:51 +08:00
// Os-NOT: -momit-leaf-frame-pointer
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Os: -Os
fix previous commit Forgot to add the '='. In cl mode, --target must have an '='. llvm-svn: 249232
2015-10-03 15:15:28 +08:00
// RUN: %clang_cl /Ot --target=i686-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Ot %s
// RUN: %clang_cl /Ot --target=x86_64-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Ot %s
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// Ot-NOT: -mdisable-fp-elim
[Driver] Refactor interaction between -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-frame-pointer Use a tri-state enum to represent shouldUseFramePointer() and shouldUseLeafFramePointer(). This simplifies the logic and fixes PR9825: -fno-omit-frame-pointer doesn't imply -mno-omit-leaf-frame-pointer. and PR24003: /Oy- /O2 should not omit leaf frame pointer: this matches MSVC x86-32. (/Oy- is a no-op on MSVC x86-64.) and: when CC1 option -mdisable-fp-elim if absent, -momit-leaf-frame-pointer can also be omitted. The new behavior matches GCC: -fomit-frame-pointer wins over -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer loses out to -momit-leaf-frame-pointer The behavior makes lots of sense. We have 4 states: - 00) leaf retained, non-leaf retained - 01) leaf retained, non-leaf omitted (this is invalid) - 10) leaf omitted, non-leaf retained (what -momit-leaf-frame-pointer was designed for) - 11) leaf omitted, non-leaf omitted "omit" options taking precedence over "no-omit" options is the only way to make 3 valid states representable with -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-pointer. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D64294 llvm-svn: 365860
2019-07-12 10:01:51 +08:00
// Ot-NOT: -momit-leaf-frame-pointer
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Ot: -O2
fix previous commit Forgot to add the '='. In cl mode, --target must have an '='. llvm-svn: 249232
2015-10-03 15:15:28 +08:00
// RUN: %clang_cl /Ox --target=i686-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Ox %s
// RUN: %clang_cl /Ox --target=x86_64-pc-windows-msvc -### -- %s 2>&1 | FileCheck -check-prefix=Ox %s
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// Ox-NOT: -mdisable-fp-elim
[Driver] Refactor interaction between -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-frame-pointer Use a tri-state enum to represent shouldUseFramePointer() and shouldUseLeafFramePointer(). This simplifies the logic and fixes PR9825: -fno-omit-frame-pointer doesn't imply -mno-omit-leaf-frame-pointer. and PR24003: /Oy- /O2 should not omit leaf frame pointer: this matches MSVC x86-32. (/Oy- is a no-op on MSVC x86-64.) and: when CC1 option -mdisable-fp-elim if absent, -momit-leaf-frame-pointer can also be omitted. The new behavior matches GCC: -fomit-frame-pointer wins over -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer loses out to -momit-leaf-frame-pointer The behavior makes lots of sense. We have 4 states: - 00) leaf retained, non-leaf retained - 01) leaf retained, non-leaf omitted (this is invalid) - 10) leaf omitted, non-leaf retained (what -momit-leaf-frame-pointer was designed for) - 11) leaf omitted, non-leaf omitted "omit" options taking precedence over "no-omit" options is the only way to make 3 valid states representable with -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-pointer. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D64294 llvm-svn: 365860
2019-07-12 10:01:51 +08:00
// Ox-NOT: -momit-leaf-frame-pointer
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// Ox: -O2
[clang-cl] Only respect /Oy- for x86_32 The /Oy- flag should have no effect for 64-bit X86, it has reliable unwind tables. llvm-svn: 245913
2015-08-25 08:46:45 +08:00
// RUN: %clang_cl --target=i686-pc-win32 /O2sy- -### -- %s 2>&1 | FileCheck -check-prefix=PR24003 %s
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// PR24003: -mdisable-fp-elim
[Driver] Refactor interaction between -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-frame-pointer Use a tri-state enum to represent shouldUseFramePointer() and shouldUseLeafFramePointer(). This simplifies the logic and fixes PR9825: -fno-omit-frame-pointer doesn't imply -mno-omit-leaf-frame-pointer. and PR24003: /Oy- /O2 should not omit leaf frame pointer: this matches MSVC x86-32. (/Oy- is a no-op on MSVC x86-64.) and: when CC1 option -mdisable-fp-elim if absent, -momit-leaf-frame-pointer can also be omitted. The new behavior matches GCC: -fomit-frame-pointer wins over -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer loses out to -momit-leaf-frame-pointer The behavior makes lots of sense. We have 4 states: - 00) leaf retained, non-leaf retained - 01) leaf retained, non-leaf omitted (this is invalid) - 10) leaf omitted, non-leaf retained (what -momit-leaf-frame-pointer was designed for) - 11) leaf omitted, non-leaf omitted "omit" options taking precedence over "no-omit" options is the only way to make 3 valid states representable with -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-pointer. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D64294 llvm-svn: 365860
2019-07-12 10:01:51 +08:00
// PR24003-NOT: -momit-leaf-frame-pointer
[clang-cl] Handle -O correctly We had multiple bugs here: - We didn't support multiple optimization options in one argument. e.g. -O2y- - We didn't correctly expand -O[12dx] to their respective options. - We treated -O1 as clang -O1 instead of clang -Os. - We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox option is *less* powerful than cl's -O2 option despite -Ox described as "Full Optimization". This fixes PR24003. llvm-svn: 243261
2015-07-27 15:32:11 +08:00
// PR24003: -Os
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Don't warn about /Oy- being unused in 64-bit builds. http://reviews.llvm.org/D18392 llvm-svn: 264163
2016-03-23 23:37:41 +08:00
// RUN: %clang_cl --target=i686-pc-win32 -Werror /Oy- /O2 -### -- %s 2>&1 | FileCheck -check-prefix=Oy_2 %s
[Driver] Refactor interaction between -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-frame-pointer Use a tri-state enum to represent shouldUseFramePointer() and shouldUseLeafFramePointer(). This simplifies the logic and fixes PR9825: -fno-omit-frame-pointer doesn't imply -mno-omit-leaf-frame-pointer. and PR24003: /Oy- /O2 should not omit leaf frame pointer: this matches MSVC x86-32. (/Oy- is a no-op on MSVC x86-64.) and: when CC1 option -mdisable-fp-elim if absent, -momit-leaf-frame-pointer can also be omitted. The new behavior matches GCC: -fomit-frame-pointer wins over -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer loses out to -momit-leaf-frame-pointer The behavior makes lots of sense. We have 4 states: - 00) leaf retained, non-leaf retained - 01) leaf retained, non-leaf omitted (this is invalid) - 10) leaf omitted, non-leaf retained (what -momit-leaf-frame-pointer was designed for) - 11) leaf omitted, non-leaf omitted "omit" options taking precedence over "no-omit" options is the only way to make 3 valid states representable with -f(no-)?omit-frame-pointer and -m(no-)?omit-leaf-pointer. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D64294 llvm-svn: 365860
2019-07-12 10:01:51 +08:00
// Oy_2-NOT: -momit-leaf-frame-pointer
[MSVC Compat] Don't omit frame pointers if /Oy- is specified before /O2 Microsoft's documentation states that specifying /Oy- after the /O[12x] options disables frame-pointer omission. What it does *not* state is that it also disables frame-pointer omission if /Oy- is specified before /O[12x]. llvm-svn: 258447
2016-01-22 07:01:11 +08:00
// Oy_2: -O2
[clang-cl] support /Oy- on aarch64 MSVC supports /Oy- on aarch64, so clang-cl should too. Patch by Nathan Froyd! Differential Revision: https://reviews.llvm.org/D57838 llvm-svn: 353402
2019-02-07 20:46:49 +08:00
// RUN: %clang_cl --target=aarch64-pc-windows-msvc -Werror /Oy- /O2 -### -- %s 2>&1 | FileCheck -check-prefix=Oy_aarch64 %s
// Oy_aarch64: -mdisable-fp-elim
// Oy_aarch64: -O2
[clang-cl] Claim ignored /O[12xd] arguments Fixes PR34809 llvm-svn: 314743
2017-10-03 08:14:03 +08:00
// RUN: %clang_cl --target=i686-pc-win32 -Werror /O2 /O2 -### -- %s 2>&1 | FileCheck -check-prefix=O2O2 %s
// O2O2: "-O2"
clang-cl: Don't warn about /Oy- being unused in 64-bit builds. http://reviews.llvm.org/D18392 llvm-svn: 264163
2016-03-23 23:37:41 +08:00
// RUN: %clang_cl /Zs -Werror /Oy -- %s 2>&1
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Don't warn about /Oy- being unused in 64-bit builds. http://reviews.llvm.org/D18392 llvm-svn: 264163
2016-03-23 23:37:41 +08:00
// RUN: %clang_cl --target=i686-pc-win32 -Werror /Oy- -### -- %s 2>&1 | FileCheck -check-prefix=Oy_ %s
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Oy_: -mdisable-fp-elim
[clang-cl] Add /Qvec and /Qvec- to control vectorization llvm-svn: 237335
2015-05-14 13:19:17 +08:00
// RUN: %clang_cl /Qvec -### -- %s 2>&1 | FileCheck -check-prefix=Qvec %s
// Qvec: -vectorize-loops
// RUN: %clang_cl /Qvec /Qvec- -### -- %s 2>&1 | FileCheck -check-prefix=Qvec_ %s
// Qvec_-NOT: -vectorize-loops
clang-cl: Support /showIncludes This option prints information about #included files to stderr. Clang could already do it, this patch just teaches the existing code about the /showIncludes style and adds the flag. Differential Revision: http://llvm-reviews.chandlerc.com/D1333 llvm-svn: 188037
2013-08-09 08:32:23 +08:00
// RUN: %clang_cl /showIncludes -### -- %s 2>&1 | FileCheck -check-prefix=showIncludes %s
// showIncludes: --show-includes
clang-cl: ignore /showIncludes when combined with /E (PR20336) Both /showIncludes and /E write to stdout. Allowing both results in interleaved output and an error when double-closing the file descriptor, intended to catch issues like this. llvm-svn: 213589
2014-07-22 07:42:07 +08:00
// RUN: %clang_cl /E /showIncludes -### -- %s 2>&1 | FileCheck -check-prefix=showIncludes_E %s
// RUN: %clang_cl /EP /showIncludes -### -- %s 2>&1 | FileCheck -check-prefix=showIncludes_E %s
Allow /showIncludes with /P r213589 was checked in as a solution to https://bugs.llvm.org/show_bug.cgi?id=20336. However, it is possible to use /EP with /P to suppress #line directives AND output to a file. There is no reason in that case to suppress /showIncludes. This was reported here: https://bugs.llvm.org/show_bug.cgi?id=34997 Differential Revision: https://reviews.llvm.org/D39104 llvm-svn: 316225
2017-10-21 03:18:30 +08:00
// RUN: %clang_cl /E /EP /showIncludes -### -- %s 2>&1 | FileCheck -check-prefix=showIncludes_E %s
[clang-cl] Print /showIncludes to stderr, if used in combination with /E, /EP or /P This replicates 'cl.exe' behavior and allows for both preprocessor output and dependency information to be extraced with a single compiler invocation. This is especially useful for compiler caching with tools like Mozilla's sccache. See: https://github.com/mozilla/sccache/issues/246 Patch By: fxb Differential Revision: https://reviews.llvm.org/D46394 llvm-svn: 331533
2018-05-04 23:58:31 +08:00
// RUN: %clang_cl /EP /P /showIncludes -### -- %s 2>&1 | FileCheck -check-prefix=showIncludes_E %s
// showIncludes_E-NOT: warning: argument unused during compilation: '--show-includes'
Allow /showIncludes with /P r213589 was checked in as a solution to https://bugs.llvm.org/show_bug.cgi?id=20336. However, it is possible to use /EP with /P to suppress #line directives AND output to a file. There is no reason in that case to suppress /showIncludes. This was reported here: https://bugs.llvm.org/show_bug.cgi?id=34997 Differential Revision: https://reviews.llvm.org/D39104 llvm-svn: 316225
2017-10-21 03:18:30 +08:00
clang-cl: Accept MSVC 2015's `/source-charset:utf-8` flag. clang already treats all inputs as utf-8. Warn if anything but utf-8 is passed. Do this by mapping source-charset to finput-charset, which already behaves like this. Slightly tweak finput-charset to accept "utf-8" case-insensitively. This matches gcc's and cl.exe's behavior, and IANA says that character set names are case-insensitive. https://reviews.llvm.org/D23807 llvm-svn: 279531
2016-08-24 00:47:09 +08:00
// /source-charset: should warn on everything except UTF-8.
// RUN: %clang_cl /source-charset:utf-16 -### -- %s 2>&1 | FileCheck -check-prefix=source-charset-utf-16 %s
Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics With this, `clang-cl /source-charset:utf-16 test.cc` now prints `invalid value 'utf-16' in '/source-charset:utf-16'` instead of `invalid value 'utf-16' in '-finput-charset=utf-16'` before, and several other clang-cl flags produce much less confusing output as well. Fixes PR29106. Since an arg and its alias can have different arg types (joined vs not) and different values (because of AliasArgs<>), I chose to give the Alias its own Arg object. For convenience, I just store the alias directly in the unaliased arg – there aren't many arg objects at runtime, so that seems ok. Finally, I changed Arg::getAsString() to use the alias's representation if it's present – that function was already documented as being the suitable function for diagnostics, and most callers already used it for diagnostics. Implementation-wise, Arg::accept() previously used to parse things as the unaliased option. The core of that switch is now extracted into a new function acceptInternal() which parses as the _aliased_ option, and the previously-intermingled unaliasing is now done as an explicit step afterwards. (This also changes one place in lld that didn't use getAsString() for diagnostics, so that that one place now also prints the flag as the user wrote it, not as it looks after it went through unaliasing.) Differential Revision: https://reviews.llvm.org/D64253 llvm-svn: 365413
2019-07-09 08:34:08 +08:00
// source-charset-utf-16: invalid value 'utf-16' in '/source-charset:utf-16'
clang-cl: Accept MSVC 2015's `/source-charset:utf-8` flag. clang already treats all inputs as utf-8. Warn if anything but utf-8 is passed. Do this by mapping source-charset to finput-charset, which already behaves like this. Slightly tweak finput-charset to accept "utf-8" case-insensitively. This matches gcc's and cl.exe's behavior, and IANA says that character set names are case-insensitive. https://reviews.llvm.org/D23807 llvm-svn: 279531
2016-08-24 00:47:09 +08:00
clang-cl: Accept MSVC 2015's `/execution-charset:utf-8` flag. Also makes -fexec-charset accept utf-8 case-insensitively. Like https://reviews.llvm.org/D23807, but for execution-charset. Also replace a few .lower() comparisons with equals_lower(). https://reviews.llvm.org/D23938 llvm-svn: 279866
2016-08-27 05:11:43 +08:00
// /execution-charset: should warn on everything except UTF-8.
// RUN: %clang_cl /execution-charset:utf-16 -### -- %s 2>&1 | FileCheck -check-prefix=execution-charset-utf-16 %s
Let unaliased Args track which Alias they were created from, and use that in Arg::getAsString() for diagnostics With this, `clang-cl /source-charset:utf-16 test.cc` now prints `invalid value 'utf-16' in '/source-charset:utf-16'` instead of `invalid value 'utf-16' in '-finput-charset=utf-16'` before, and several other clang-cl flags produce much less confusing output as well. Fixes PR29106. Since an arg and its alias can have different arg types (joined vs not) and different values (because of AliasArgs<>), I chose to give the Alias its own Arg object. For convenience, I just store the alias directly in the unaliased arg – there aren't many arg objects at runtime, so that seems ok. Finally, I changed Arg::getAsString() to use the alias's representation if it's present – that function was already documented as being the suitable function for diagnostics, and most callers already used it for diagnostics. Implementation-wise, Arg::accept() previously used to parse things as the unaliased option. The core of that switch is now extracted into a new function acceptInternal() which parses as the _aliased_ option, and the previously-intermingled unaliasing is now done as an explicit step afterwards. (This also changes one place in lld that didn't use getAsString() for diagnostics, so that that one place now also prints the flag as the user wrote it, not as it looks after it went through unaliasing.) Differential Revision: https://reviews.llvm.org/D64253 llvm-svn: 365413
2019-07-09 08:34:08 +08:00
// execution-charset-utf-16: invalid value 'utf-16' in '/execution-charset:utf-16'
clang-cl: Accept MSVC 2015's `/execution-charset:utf-8` flag. Also makes -fexec-charset accept utf-8 case-insensitively. Like https://reviews.llvm.org/D23807, but for execution-charset. Also replace a few .lower() comparisons with equals_lower(). https://reviews.llvm.org/D23938 llvm-svn: 279866
2016-08-27 05:11:43 +08:00
//
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /Umymacro -### -- %s 2>&1 | FileCheck -check-prefix=U %s
// RUN: %clang_cl /U mymacro -### -- %s 2>&1 | FileCheck -check-prefix=U %s
// U: "-U" "mymacro"
clang-cl: Support MSVC2015's /validate-charset flag. Clang always assumes that files are utf-8. If an invalidly encoded character is used in an identifier, clang always errors. If it's used in a character literal, clang warns Winvalid-source-encoding (on by default). Clang never checks the encoding of things in comments (adding this seems like a nice feature if it doesn't impact performance). For cl.exe /utf-8 (which enables /validate-charset), if a bad character is used in an identifier, it emits both an error and a warning. If it's used in a literal or a comment, it emits a warning. So mapping /validate-charset to -Winvalid-source-encoding seems like a fairly decent fit. https://reviews.llvm.org/D23945 llvm-svn: 279872
2016-08-27 05:51:14 +08:00
// RUN: %clang_cl /validate-charset -### -- %s 2>&1 | FileCheck -check-prefix=validate-charset %s
// validate-charset: -Winvalid-source-encoding
// RUN: %clang_cl /validate-charset- -### -- %s 2>&1 | FileCheck -check-prefix=validate-charset_ %s
// validate-charset_: -Wno-invalid-source-encoding
Driver: cleanup /vd2 test /vd2 is not ignored anymore, remove it from the ignored list. Add a test to ensure that it does the right thing. llvm-svn: 204563
2014-03-24 01:47:18 +08:00
// RUN: %clang_cl /vd2 -### -- %s 2>&1 | FileCheck -check-prefix=VD2 %s
// VD2: -vtordisp-mode=2
MS ABI: Add support for the -vm{b,g,s,m,v} flags These flags control the inheritance model initially used by the translation unit. Differential Revision: http://llvm-reviews.chandlerc.com/D2741 llvm-svn: 201175
2014-02-12 05:05:00 +08:00
// RUN: %clang_cl /vmg -### -- %s 2>&1 | FileCheck -check-prefix=VMG %s
// VMG: "-fms-memptr-rep=virtual"
// RUN: %clang_cl /vmg /vms -### -- %s 2>&1 | FileCheck -check-prefix=VMS %s
// VMS: "-fms-memptr-rep=single"
// RUN: %clang_cl /vmg /vmm -### -- %s 2>&1 | FileCheck -check-prefix=VMM %s
// VMM: "-fms-memptr-rep=multiple"
// RUN: %clang_cl /vmg /vmv -### -- %s 2>&1 | FileCheck -check-prefix=VMV %s
// VMV: "-fms-memptr-rep=virtual"
// RUN: %clang_cl /vmg /vmb -### -- %s 2>&1 | FileCheck -check-prefix=VMB %s
// VMB: '/vmg' not allowed with '/vmb'
// RUN: %clang_cl /vmg /vmm /vms -### -- %s 2>&1 | FileCheck -check-prefix=VMX %s
// VMX: '/vms' not allowed with '/vmm'
Revert "Revert r229082 for a bit, it caused PR22577." This reverts commit r229123. It was a red herring, the bug was present without r229082. llvm-svn: 229205
2015-02-14 09:35:12 +08:00
// RUN: %clang_cl /volatile:iso -### -- %s 2>&1 | FileCheck -check-prefix=VOLATILE-ISO %s
// VOLATILE-ISO-NOT: "-fms-volatile"
// RUN: %clang_cl /volatile:ms -### -- %s 2>&1 | FileCheck -check-prefix=VOLATILE-MS %s
// VOLATILE-MS: "-fms-volatile"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /W0 -### -- %s 2>&1 | FileCheck -check-prefix=W0 %s
// W0: -w
// RUN: %clang_cl /W1 -### -- %s 2>&1 | FileCheck -check-prefix=W1 %s
// RUN: %clang_cl /W2 -### -- %s 2>&1 | FileCheck -check-prefix=W1 %s
// RUN: %clang_cl /W3 -### -- %s 2>&1 | FileCheck -check-prefix=W1 %s
[clang-cl] Let /W4 map to -Wall -Wextra instead of just -Wall. There's no way to make a flag alias to two flags, so add a /WCL4 flag that maps to the All, Extra diag groups. Fixes PR25563. http://reviews.llvm.org/D15350 llvm-svn: 255382
2015-12-12 06:31:16 +08:00
// RUN: %clang_cl /W4 -### -- %s 2>&1 | FileCheck -check-prefix=W4 %s
[clang-cl] Alias /Wall to -Weverything cl interprets this option to mean enable every supported warning, which is what Clang's -Weverything flag does. llvm-svn: 319116
2017-11-28 07:42:20 +08:00
// RUN: %clang_cl /Wall -### -- %s 2>&1 | FileCheck -check-prefix=Weverything %s
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// W1: -Wall
[clang-cl] Let /W4 map to -Wall -Wextra instead of just -Wall. There's no way to make a flag alias to two flags, so add a /WCL4 flag that maps to the All, Extra diag groups. Fixes PR25563. http://reviews.llvm.org/D15350 llvm-svn: 255382
2015-12-12 06:31:16 +08:00
// W4: -WCL4
[clang-cl] Alias /Wall to -Weverything cl interprets this option to mean enable every supported warning, which is what Clang's -Weverything flag does. llvm-svn: 319116
2017-11-28 07:42:20 +08:00
// Weverything: -Weverything
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /WX -### -- %s 2>&1 | FileCheck -check-prefix=WX %s
// WX: -Werror
// RUN: %clang_cl /WX- -### -- %s 2>&1 | FileCheck -check-prefix=WX_ %s
// WX_: -Wno-error
// RUN: %clang_cl /w -### -- %s 2>&1 | FileCheck -check-prefix=w %s
// w: -w
clang-cl: Add support for /Zp CL's /Zp flag is analogous to GCC's -fpack-struct, it controls the default maximum alignment of records. Differential Revision: http://reviews.llvm.org/D4671 llvm-svn: 213958
2014-07-26 01:30:10 +08:00
// RUN: %clang_cl /Zp -### -- %s 2>&1 | FileCheck -check-prefix=ZP %s
// ZP: -fpack-struct=1
// RUN: %clang_cl /Zp2 -### -- %s 2>&1 | FileCheck -check-prefix=ZP2 %s
// ZP2: -fpack-struct=2
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// RUN: %clang_cl /Zs -### -- %s 2>&1 | FileCheck -check-prefix=Zs %s
// Zs: -fsyntax-only
clang-cl: Add /FI (forced include) as an alias for -include Patch by Jeff Muizelaar, with added test case. llvm-svn: 191442
2013-09-27 01:41:14 +08:00
// RUN: %clang_cl /FIasdf.h -### -- %s 2>&1 | FileCheck -check-prefix=FI %s
// FI: "-include" "asdf.h"
Add support for the separate version of /FI. Patch by Jeff Muizelaar. llvm-svn: 193642
2013-10-30 03:42:01 +08:00
// RUN: %clang_cl /FI asdf.h -### -- %s 2>&1 | FileCheck -check-prefix=FI_ %s
// FI_: "-include" "asdf.h"
[clang-cl] /EHc should not effect functions with explicit exception specifications Functions with an explicit exception specification have their behavior dictated by the specification. The additional /EHc behavior only comes into play if no exception specification is given. llvm-svn: 262198
2016-02-29 09:40:36 +08:00
// RUN: %clang_cl /TP /c -### -- %s 2>&1 | FileCheck -check-prefix=NO-GX %s
Don't enable /GX by default The /GX flag is disabled unless explicitly specified on the command line. This partially addresses PR26698. llvm-svn: 261537
2016-02-23 01:44:51 +08:00
// NO-GX-NOT: "-fcxx-exceptions" "-fexceptions"
[clang-cl] /EHc should not effect functions with explicit exception specifications Functions with an explicit exception specification have their behavior dictated by the specification. The additional /EHc behavior only comes into play if no exception specification is given. llvm-svn: 262198
2016-02-29 09:40:36 +08:00
// RUN: %clang_cl /TP /c /GX -### -- %s 2>&1 | FileCheck -check-prefix=GX %s
[MSVC Compat] Add support for /GX, /GX- These are legacy flags which map to /EHsc and /EHs-c- respectively. llvm-svn: 261424
2016-02-20 17:23:44 +08:00
// GX: "-fcxx-exceptions" "-fexceptions"
[clang-cl] /EHc should not effect functions with explicit exception specifications Functions with an explicit exception specification have their behavior dictated by the specification. The additional /EHc behavior only comes into play if no exception specification is given. llvm-svn: 262198
2016-02-29 09:40:36 +08:00
// RUN: %clang_cl /TP /c /GX /GX- -### -- %s 2>&1 | FileCheck -check-prefix=GX_ %s
[MSVC Compat] Add support for /GX, /GX- These are legacy flags which map to /EHsc and /EHs-c- respectively. llvm-svn: 261424
2016-02-20 17:23:44 +08:00
// GX_-NOT: "-fcxx-exceptions" "-fexceptions"
clang-cl: Make /d1PP an alias for -dD (PR36446) llvm-svn: 325571
2018-02-20 18:47:14 +08:00
// RUN: %clang_cl /d1PP -### -- %s 2>&1 | FileCheck -check-prefix=d1PP %s
// d1PP: -dD
clang-cl: Make -W a core option so we can adjust clang warnings. llvm-svn: 189882
2013-09-04 07:18:43 +08:00
// We forward any unrecognized -W diagnostic options to cc1.
// RUN: %clang_cl -Wunused-pragmas -### -- %s 2>&1 | FileCheck -check-prefix=WJoined %s
// WJoined: "-cc1"
// WJoined: "-Wunused-pragmas"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: Disable TBAA by default for MSVC compatibility MSVC doesn't have an option to enable TBAA, so make -fstrict-aliasing and -fno-strict-aliasing available in clang-cl. llvm-svn: 205924
2014-04-10 04:07:39 +08:00
// We recognize -f[no-]strict-aliasing.
// RUN: %clang_cl -c -### -- %s 2>&1 | FileCheck -check-prefix=DEFAULTSTRICT %s
// DEFAULTSTRICT: "-relaxed-aliasing"
// RUN: %clang_cl -c -fstrict-aliasing -### -- %s 2>&1 | FileCheck -check-prefix=STRICT %s
// STRICT-NOT: "-relaxed-aliasing"
// RUN: %clang_cl -c -fno-strict-aliasing -### -- %s 2>&1 | FileCheck -check-prefix=NOSTRICT %s
// NOSTRICT: "-relaxed-aliasing"
Support -fno-delayed-template-parsing in clang-cl.exe Summary: This change adds support for the -fno-delayed-template-parsing option in clang-cl.exe. This allows developers using clang-cl.exe to opt out of emulation of MSVC's non-conformant template instantiation implementation while continuing to use clang-cl.exe for its emulation of cl.exe command-line options. The default behavior of clang-cl.exe (-fdelayed-template-parsing) is unchanged. The MSVC Standard Library implementation uses clang-cl.exe with this switch in its tests to ensure that the library headers work on compilers with the conformant two-phase-lookup behavior. Reviewers: majnemer, cfe-commits, DaveBartolomeo Differential Revision: https://reviews.llvm.org/D22275 llvm-svn: 290990
2017-01-05 03:15:53 +08:00
// We recognize -f[no-]delayed-template-parsing.
clang-cl: Support the /Zc:twoPhase[-] command-line option (PR32680) It sounds like MSVC is adding support for two-phase name lookup in a future version, enabled by this flag (see bug). Differential Revision: https://reviews.llvm.org/D32138 llvm-svn: 300501
2017-04-18 05:28:36 +08:00
// /Zc:twoPhase[-] has the opposite meaning.
Support -fno-delayed-template-parsing in clang-cl.exe Summary: This change adds support for the -fno-delayed-template-parsing option in clang-cl.exe. This allows developers using clang-cl.exe to opt out of emulation of MSVC's non-conformant template instantiation implementation while continuing to use clang-cl.exe for its emulation of cl.exe command-line options. The default behavior of clang-cl.exe (-fdelayed-template-parsing) is unchanged. The MSVC Standard Library implementation uses clang-cl.exe with this switch in its tests to ensure that the library headers work on compilers with the conformant two-phase-lookup behavior. Reviewers: majnemer, cfe-commits, DaveBartolomeo Differential Revision: https://reviews.llvm.org/D22275 llvm-svn: 290990
2017-01-05 03:15:53 +08:00
// RUN: %clang_cl -c -### -- %s 2>&1 | FileCheck -check-prefix=DELAYEDDEFAULT %s
// DELAYEDDEFAULT: "-fdelayed-template-parsing"
// RUN: %clang_cl -c -fdelayed-template-parsing -### -- %s 2>&1 | FileCheck -check-prefix=DELAYEDON %s
clang-cl: Support the /Zc:twoPhase[-] command-line option (PR32680) It sounds like MSVC is adding support for two-phase name lookup in a future version, enabled by this flag (see bug). Differential Revision: https://reviews.llvm.org/D32138 llvm-svn: 300501
2017-04-18 05:28:36 +08:00
// RUN: %clang_cl -c /Zc:twoPhase- -### -- %s 2>&1 | FileCheck -check-prefix=DELAYEDON %s
Support -fno-delayed-template-parsing in clang-cl.exe Summary: This change adds support for the -fno-delayed-template-parsing option in clang-cl.exe. This allows developers using clang-cl.exe to opt out of emulation of MSVC's non-conformant template instantiation implementation while continuing to use clang-cl.exe for its emulation of cl.exe command-line options. The default behavior of clang-cl.exe (-fdelayed-template-parsing) is unchanged. The MSVC Standard Library implementation uses clang-cl.exe with this switch in its tests to ensure that the library headers work on compilers with the conformant two-phase-lookup behavior. Reviewers: majnemer, cfe-commits, DaveBartolomeo Differential Revision: https://reviews.llvm.org/D22275 llvm-svn: 290990
2017-01-05 03:15:53 +08:00
// DELAYEDON: "-fdelayed-template-parsing"
// RUN: %clang_cl -c -fno-delayed-template-parsing -### -- %s 2>&1 | FileCheck -check-prefix=DELAYEDOFF %s
clang-cl: Support the /Zc:twoPhase[-] command-line option (PR32680) It sounds like MSVC is adding support for two-phase name lookup in a future version, enabled by this flag (see bug). Differential Revision: https://reviews.llvm.org/D32138 llvm-svn: 300501
2017-04-18 05:28:36 +08:00
// RUN: %clang_cl -c /Zc:twoPhase -### -- %s 2>&1 | FileCheck -check-prefix=DELAYEDOFF %s
Support -fno-delayed-template-parsing in clang-cl.exe Summary: This change adds support for the -fno-delayed-template-parsing option in clang-cl.exe. This allows developers using clang-cl.exe to opt out of emulation of MSVC's non-conformant template instantiation implementation while continuing to use clang-cl.exe for its emulation of cl.exe command-line options. The default behavior of clang-cl.exe (-fdelayed-template-parsing) is unchanged. The MSVC Standard Library implementation uses clang-cl.exe with this switch in its tests to ensure that the library headers work on compilers with the conformant two-phase-lookup behavior. Reviewers: majnemer, cfe-commits, DaveBartolomeo Differential Revision: https://reviews.llvm.org/D22275 llvm-svn: 290990
2017-01-05 03:15:53 +08:00
// DELAYEDOFF-NOT: "-fdelayed-template-parsing"
Driver: support `/Zc:char8_t` and `/Zc:char8_t-` Update the `cl` emulation to support the `/Zc:char8_t[-]?` options as per the MSVC 2019.1 toolset. These are aliases for `-fchar8_t` and `-fno-char8_t`. llvm-svn: 361859
2019-05-29 02:26:00 +08:00
// RUN: %clang_cl -c -### /std:c++latest -- %s 2>&1 | FileCheck -check-prefix CHECK-LATEST-CHAR8_T %s
// CHECK-LATEST-CHAR8_T-NOT: "-fchar8_t"
// RUN: %clang_cl -c -### /Zc:char8_t -- %s 2>&1 | FileCheck -check-prefix CHECK-CHAR8_T %s
// CHECK-CHAR8_T: "-fchar8_t"
// RUN: %clang_cl -c -### /Zc:char8_t- -- %s 2>&1 | FileCheck -check-prefix CHECK-CHAR8_T_ %s
// CHECK-CHAR8_T_: "-fno-char8_t"
Add clang-cl alias to allow users to disable c4005 If we ever want three or more aliases, at that point we should put MSVC warning ids in DiagnosticGroups.td. We can use that to support #pragma warning. llvm-svn: 205598
2014-04-04 09:36:55 +08:00
// For some warning ids, we can map from MSVC warning to Clang warning.
clang-cl: Add an alias for /wd4100 llvm-svn: 255655
2015-12-16 01:07:16 +08:00
// RUN: %clang_cl -wd4005 -wd4100 -wd4910 -wd4996 -### -- %s 2>&1 | FileCheck -check-prefix=Wno %s
clang-cl: Map /wd4996 to -Wno-deprecated-declarations This is typically used to suppress warnings about calling snprintf and other "deprecated" POSIX functions. Accepting this flag helps avoid tons of useless warnings when trying out clang-cl on a new project. Patch by Scott Graham! llvm-svn: 229583
2015-02-18 07:28:19 +08:00
// Wno: "-cc1"
// Wno: "-Wno-macro-redefined"
clang-cl: Add an alias for /wd4100 llvm-svn: 255655
2015-12-16 01:07:16 +08:00
// Wno: "-Wno-unused-parameter"
clang-cl: Add an alias for /wd4910 llvm-svn: 239548
2015-06-12 02:14:11 +08:00
// Wno: "-Wno-dllexport-explicit-instantiation-decl"
clang-cl: Add an alias for /wd4100 llvm-svn: 255655
2015-12-16 01:07:16 +08:00
// Wno: "-Wno-deprecated-declarations"
clang-cl: ignore compile-only options in link-only invocations. Previously we would warn about unused arguments such as /MD when linking. Clang already has logic to ignore compile-only options, e.g. for -D and -U. This patch extends that to include clang-cl's compile-only options too. Also, some clang-cl options should always be ignored. Doing this earlier means they get ignored both for compilation and link-only invocations. llvm-svn: 190825
2013-09-17 08:03:41 +08:00
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Ignored options. Check that we don't get "unused during compilation" errors.
clang-cl: Correctly ignore /openmp- (PR22748) llvm-svn: 231026
2015-03-03 06:09:05 +08:00
// RUN: %clang_cl /c \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /analyze- \
clang-cl: Don't warn on /bigobj flag LLVM r217812 made it so that clang-cl implicitly creates bigobj files when needed, independent of this flag. It looks like cl has this flag to produce obj flags compatible with MSVS 2003's linker by default, something we don't care about. Since clang-cl always has /bigobj behavior, don't warn that the flag is unused, just ignore it silently. llvm-svn: 248034
2015-09-19 04:49:33 +08:00
// RUN: /bigobj \
clang-cl: ignore /cgthreads (PR21894) llvm-svn: 224201
2014-12-14 06:24:16 +08:00
// RUN: /cgthreads4 \
// RUN: /cgthreads8 \
clang-cl: Silently ignore /d2FastFail flag. It's some debugging flag for cl.exe related to how it writes crash dumps. llvm-svn: 264774
2016-03-30 03:41:02 +08:00
// RUN: /d2FastFail \
clang-cl: Ignore the new /Zo[-] option (PR21571) Also fix the ignored options test which didn't fail properly on unknown options. llvm-svn: 222013
2014-11-15 02:24:08 +08:00
// RUN: /d2Zi+ \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /errorReport:foo \
clang-cl: Accept MSVC 2015's `/execution-charset:utf-8` flag. Also makes -fexec-charset accept utf-8 case-insensitively. Like https://reviews.llvm.org/D23807, but for execution-charset. Also replace a few .lower() comparisons with equals_lower(). https://reviews.llvm.org/D23938 llvm-svn: 279866
2016-08-27 05:11:43 +08:00
// RUN: /execution-charset:utf-8 \
clang-cl: Move /FC from "Unsupported" to "Ignored" list. /FC affects if diagnostics print with full paths and if __FILE__ expands with a full path. clang-cl does both of these two by default. llvm-svn: 263953
2016-03-22 01:19:31 +08:00
// RUN: /FC \
clang-cl: Ignore /Fd silently While it's true that we don't create the PDB as requested on the command line, this is a well-documented limitation. Warning about it doesn't help people using legacy build systems with clang-cl, and it makes the clang-cl self-host very noisy. llvm-svn: 230527
2015-02-26 03:17:50 +08:00
// RUN: /Fdfoo \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /FS \
clang-cl: Make /Gd ignored instead of unsupported /Gd is the default calling convention setting, so we don't need to take any action. llvm-svn: 224200
2014-12-14 06:13:23 +08:00
// RUN: /Gd \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /GF \
// RUN: /GS- \
// RUN: /kernel- \
// RUN: /nologo \
clang-cl: Accept (and ignore) /Zc:__cplusplus. See https://blogs.msdn.microsoft.com/vcblog/2018/04/09/msvc-now-correctly-reports-__cplusplus/ clang-cl already sets __cplusplus to the correct value, so we can just ignore this flag. Also add test coverage for a few more accepted-but-ignored flags. https://reviews.llvm.org/D45877 llvm-svn: 330427
2018-04-20 21:10:44 +08:00
// RUN: /Og \
clang-cl: Correctly ignore /openmp- (PR22748) llvm-svn: 231026
2015-03-03 06:09:05 +08:00
// RUN: /openmp- \
clang-cl: Parse /permissive-, /Bt, Bt+ (PR32672) llvm-svn: 323330
2018-01-24 23:18:12 +08:00
// RUN: /permissive- \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /RTC1 \
// RUN: /sdl \
// RUN: /sdl- \
clang-cl: Accept MSVC 2015's `/source-charset:utf-8` flag. clang already treats all inputs as utf-8. Warn if anything but utf-8 is passed. Do this by mapping source-charset to finput-charset, which already behaves like this. Slightly tweak finput-charset to accept "utf-8" case-insensitively. This matches gcc's and cl.exe's behavior, and IANA says that character set names are case-insensitive. https://reviews.llvm.org/D23807 llvm-svn: 279531
2016-08-24 00:47:09 +08:00
// RUN: /source-charset:utf-8 \
clang-cl: Accept MSVC2015's '/utf-8' flag. Clang always behaves as if that's passed, so just ignore the flag. llvm-svn: 279869
2016-08-27 05:26:29 +08:00
// RUN: /utf-8 \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /vmg \
clang-cl: Fix handling of the /volatile flag (PR21893) The /volatile:iso flag is our default behaviour, so it can be ignored. Parse /volatile:ms as unsupported. llvm-svn: 224202
2014-12-14 06:44:46 +08:00
// RUN: /volatile:iso \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /w12345 \
// RUN: /wd1234 \
clang-cl: Accept (and ignore) /Zc:__cplusplus. See https://blogs.msdn.microsoft.com/vcblog/2018/04/09/msvc-now-correctly-reports-__cplusplus/ clang-cl already sets __cplusplus to the correct value, so we can just ignore this flag. Also add test coverage for a few more accepted-but-ignored flags. https://reviews.llvm.org/D45877 llvm-svn: 330427
2018-04-20 21:10:44 +08:00
// RUN: /Zc:__cplusplus \
// RUN: /Zc:auto \
// RUN: /Zc:forScope \
// RUN: /Zc:inline \
// RUN: /Zc:rvalueCast \
// RUN: /Zc:ternary \
// RUN: /Zc:wchar_t \
// RUN: /Zm \
clang-cl: Ignore the new /Zo[-] option (PR21571) Also fix the ignored options test which didn't fail properly on unknown options. llvm-svn: 222013
2014-11-15 02:24:08 +08:00
// RUN: /Zo \
// RUN: /Zo- \
Try to fix the cl-options.c test on ARM bots The test was failing because clang-cl changes the default triple to target MSVC-style Win32. This is kind of wonky, but hasn't been a problem until we started warning: warning: unknown platform, assuming -mfloat-abi=soft Some of the tests in cl-options.c were running with -Werror, causing them to fail. Fixing this by FileCheck-ifying those tests instead of using -Werror. llvm-svn: 205049
2014-03-29 04:45:05 +08:00
// RUN: -### -- %s 2>&1 | FileCheck -check-prefix=IGNORED %s
// IGNORED-NOT: argument unused during compilation
clang-cl: Ignore the new /Zo[-] option (PR21571) Also fix the ignored options test which didn't fail properly on unknown options. llvm-svn: 222013
2014-11-15 02:24:08 +08:00
// IGNORED-NOT: no such file or directory
clang-cl: Correctly ignore /openmp- (PR22748) llvm-svn: 231026
2015-03-03 06:09:05 +08:00
// Don't confuse /openmp- with the /o flag:
// IGNORED-NOT: "-o" "penmp-.obj"
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
clang-cl: ignore compile-only options in link-only invocations. Previously we would warn about unused arguments such as /MD when linking. Clang already has logic to ignore compile-only options, e.g. for -D and -U. This patch extends that to include clang-cl's compile-only options too. Also, some clang-cl options should always be ignored. Doing this earlier means they get ignored both for compilation and link-only invocations. llvm-svn: 190825
2013-09-17 08:03:41 +08:00
// Ignored options and compile-only options are ignored for link jobs.
cl-options.c just use touch to create that .obj file llvm-svn: 190832
2013-09-17 08:50:43 +08:00
// RUN: touch %t.obj
clang-cl: ignore compile-only options in link-only invocations. Previously we would warn about unused arguments such as /MD when linking. Clang already has logic to ignore compile-only options, e.g. for -D and -U. This patch extends that to include clang-cl's compile-only options too. Also, some clang-cl options should always be ignored. Doing this earlier means they get ignored both for compilation and link-only invocations. llvm-svn: 190825
2013-09-17 08:03:41 +08:00
// RUN: %clang_cl /nologo -### -- %t.obj 2>&1 | FileCheck -check-prefix=LINKUNUSED %s
// RUN: %clang_cl /Dfoo -### -- %t.obj 2>&1 | FileCheck -check-prefix=LINKUNUSED %s
// RUN: %clang_cl /MD -### -- %t.obj 2>&1 | FileCheck -check-prefix=LINKUNUSED %s
// LINKUNUSED-NOT: argument unused during compilation
Support suppressing unused arguments warnings as a core option so that it works in the CL flavor driver. llvm-svn: 190040
2013-09-05 18:09:03 +08:00
// Support ignoring warnings about unused arguments.
// RUN: %clang_cl /Abracadabra -Qunused-arguments -### -- %s 2>&1 | FileCheck -check-prefix=UNUSED %s
Try to fix the cl-options.c test on ARM bots The test was failing because clang-cl changes the default triple to target MSVC-style Win32. This is kind of wonky, but hasn't been a problem until we started warning: warning: unknown platform, assuming -mfloat-abi=soft Some of the tests in cl-options.c were running with -Werror, causing them to fail. Fixing this by FileCheck-ifying those tests instead of using -Werror. llvm-svn: 205049
2014-03-29 04:45:05 +08:00
// UNUSED-NOT: argument unused during compilation
Support suppressing unused arguments warnings as a core option so that it works in the CL flavor driver. llvm-svn: 190040
2013-09-05 18:09:03 +08:00
Re-commit r187637: "clang-cl: add more options" > This adds a bunch of options to clang-cl. Notably, this includes > all the options that get passed when doing a default build of a > command-line project with msbuild.exe in Debug and Release modes, > and I believe all flags from Reid's original patch. The original commit was reverted in r187640 after it broke the Mac build. This should now be fixed, by Clang r187668, LLVM r187675, and putting a -- before %s in the test. llvm-svn: 187679
2013-08-03 06:24:50 +08:00
// Unsupported but parsed options. Check that we don't error on them.
// (/Zs is for syntax-only)
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: %clang_cl /Zs \
clang-cl: Parse /Qspectre and a few other missing options (PR40964) llvm-svn: 355489
2019-03-06 17:38:04 +08:00
// RUN: /await \
// RUN: /constexpr:depth1000 /constexpr:backtrace1000 /constexpr:steps1000 \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /AIfoo \
[clang-cl] Ignore space-separated /AI arguments The /AI flag is for #using directives, which I don't think we support. This is consistent with how the /I flag is handled by MSVC. Add a test for it. Differential Revision: https://reviews.llvm.org/D57189 llvm-svn: 352119
2019-01-25 06:26:51 +08:00
// RUN: /AI foo_does_not_exist \
clang-cl: Parse /permissive-, /Bt, Bt+ (PR32672) llvm-svn: 323330
2018-01-24 23:18:12 +08:00
// RUN: /Bt \
// RUN: /Bt+ \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /clr:pure \
clang-cl : Parse all /d2 options We will now warn about such options being unused, which is better than the current "no such file or directory: '/d2foo'" errors. Note that we can still handle specific flags separately, e.g. we were already ignoring /d2FastFail and /d2Zi+ llvm-svn: 355682
2019-03-08 18:00:42 +08:00
// RUN: /d2FH4 \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /docname \
// RUN: /EHsc \
clang-cl: Fix parsing of the /F option (PR41405) llvm-svn: 358087
2019-04-10 22:27:47 +08:00
// RUN: /F 42 \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /FA \
// RUN: /FAc \
// RUN: /Fafilename \
// RUN: /FAs \
// RUN: /FAu \
// RUN: /favor:blend \
// RUN: /Fifoo \
// RUN: /Fmfoo \
// RUN: /FpDebug\main.pch \
// RUN: /Frfoo \
// RUN: /FRfoo \
// RUN: /FU foo \
// RUN: /Fx \
// RUN: /G1 \
// RUN: /G2 \
// RUN: /GA \
// RUN: /Gd \
// RUN: /Ge \
// RUN: /Gh \
// RUN: /GH \
// RUN: /GL \
// RUN: /GL- \
// RUN: /Gm \
// RUN: /Gm- \
// RUN: /Gr \
// RUN: /GS \
// RUN: /GT \
// RUN: /GX \
clang-cl: Add unsupported /Gv option (PR21892) We don't currently support any of the calling convention options. llvm-svn: 224199
2014-12-14 06:06:23 +08:00
// RUN: /Gv \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /Gz \
// RUN: /GZ \
// RUN: /H \
// RUN: /homeparams \
// RUN: /hotpatch \
clang-cl: Parse the new /JMC flag llvm-svn: 339008
2018-08-06 19:34:46 +08:00
// RUN: /JMC \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /kernel \
// RUN: /LN \
// RUN: /MP \
// RUN: /o foo.obj \
// RUN: /ofoo.obj \
// RUN: /openmp \
clang-cl: Parse /openmp:experimental It was added to the MS docs recently here: https://github.com/MicrosoftDocs/cpp-docs/commit/3951085ab722fbb488ca40864f4a0553f7b71855 llvm-svn: 358570
2019-04-17 18:05:58 +08:00
// RUN: /openmp:experimental \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /Qfast_transcendentals \
// RUN: /QIfist \
// RUN: /Qimprecise_fwaits \
// RUN: /Qpar \
clang-cl: Parse /Qspectre and a few other missing options (PR40964) llvm-svn: 355489
2019-03-06 17:38:04 +08:00
// RUN: /Qpar-report:1 \
// RUN: /Qsafe_fp_loads \
// RUN: /Qspectre \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /Qvec-report:2 \
// RUN: /u \
// RUN: /V \
clang-cl: Fix handling of the /volatile flag (PR21893) The /volatile:iso flag is our default behaviour, so it can be ignored. Parse /volatile:ms as unsupported. llvm-svn: 224202
2014-12-14 06:44:46 +08:00
// RUN: /volatile:ms \
clang-cl: Make the driver parse all(?) msvc flags Even if we don't support a flag, we should be able to parse it to provide a better error message than the current default "error: no such file or directory: '/foo'" (which we should probably also tweak, btw). This also tries to clean up the test file a bit. llvm-svn: 194837
2013-11-16 02:29:58 +08:00
// RUN: /wfoo \
// RUN: /WL \
// RUN: /Wp64 \
// RUN: /X \
// RUN: /Y- \
// RUN: /Yc \
// RUN: /Ycstdafx.h \
// RUN: /Yd \
// RUN: /Yl- \
// RUN: /Ylfoo \
// RUN: /Yustdafx.h \
// RUN: /Z7 \
// RUN: /Za \
// RUN: /Ze \
// RUN: /Zg \
// RUN: /Zi \
// RUN: /ZI \
// RUN: /Zl \
// RUN: /ZW:nostdlib \
// RUN: -- %s 2>&1
clang-cl: Expose the -Xclang option llvm-svn: 188685
2013-08-20 02:32:59 +08:00
// We support -Xclang for forwarding options to cc1.
// RUN: %clang_cl -Xclang hellocc1 -### -- %s 2>&1 | FileCheck -check-prefix=Xclang %s
// Xclang: "-cc1"
// Xclang: "hellocc1"
clang-cl: ignore compile-only options in link-only invocations. Previously we would warn about unused arguments such as /MD when linking. Clang already has logic to ignore compile-only options, e.g. for -D and -U. This patch extends that to include clang-cl's compile-only options too. Also, some clang-cl options should always be ignored. Doing this earlier means they get ignored both for compilation and link-only invocations. llvm-svn: 190825
2013-09-17 08:03:41 +08:00
clang-cl: Warn about /U flags that look like filenames (PR31662) Both on Mac and Windows, it's common to have a 'Users' directory in the root of the filesystem, so one might specify a filename as '/Users/me/myfile.c'. clang-cl (as well as MSVC's cl.exe) will interpret that as invoking the '/U' option, which is probably not what the user wanted. Add a warning about this. Differential Revision: https://reviews.llvm.org/D29198 llvm-svn: 293305
2017-01-28 01:09:41 +08:00
// Files under /Users are often confused with the /U flag. (This could happen
// for other flags too, but this is the one people run into.)
// RUN: %clang_cl /c /Users/me/myfile.c -### 2>&1 | FileCheck -check-prefix=SlashU %s
// SlashU: warning: '/Users/me/myfile.c' treated as the '/U' option
// SlashU: note: Use '--' to treat subsequent arguments as filenames
Driver: Handle /GR- in a compatible way with MSVC There are slight differences between /GR- and -fno-rtti which made mapping one to the other inappropriate. -fno-rtti disables dynamic_cast, typeid, and does not emit RTTI related information for the v-table. /GR- does not generate complete object locators and thus will not reference them in vftables. However, constructs like dynamic_cast and typeid are permitted. This should bring our implementation of RTTI up to semantic parity with MSVC modulo bugs. llvm-svn: 212138
2014-07-02 06:24:56 +08:00
// RTTI is on by default. /GR- controls -fno-rtti-data.
// RUN: %clang_cl /c /GR- -### -- %s 2>&1 | FileCheck -check-prefix=NoRTTI %s
// NoRTTI: "-fno-rtti-data"
// NoRTTI-NOT: "-fno-rtti"
clang-cl: use -fno-rtti by default Generating RTTI in the MS ABI is currently not supported, and the failures are confusing to users, so let's disable it by default for now. llvm-svn: 202178
2014-02-26 02:36:22 +08:00
// RUN: %clang_cl /c /GR -### -- %s 2>&1 | FileCheck -check-prefix=RTTI %s
Driver: Handle /GR- in a compatible way with MSVC There are slight differences between /GR- and -fno-rtti which made mapping one to the other inappropriate. -fno-rtti disables dynamic_cast, typeid, and does not emit RTTI related information for the v-table. /GR- does not generate complete object locators and thus will not reference them in vftables. However, constructs like dynamic_cast and typeid are permitted. This should bring our implementation of RTTI up to semantic parity with MSVC modulo bugs. llvm-svn: 212138
2014-07-02 06:24:56 +08:00
// RTTI-NOT: "-fno-rtti-data"
clang-cl: use -fno-rtti by default Generating RTTI in the MS ABI is currently not supported, and the failures are confusing to users, so let's disable it by default for now. llvm-svn: 202178
2014-02-26 02:36:22 +08:00
// RTTI-NOT: "-fno-rtti"
MS ABI: Implement driver-level support for thread-safe statics Decide whether or not to use thread-safe statics depending on whether or not we have an explicit request from the driver. If we don't have an explicit request, infer which behavior to use depending on the compatibility version we are targeting. N.B. CodeGen support is still ongoing. llvm-svn: 232906
2015-03-22 16:39:22 +08:00
// thread safe statics are off for versions < 19.
Get default -fms-compatibility-version from cl.exe's version -fms-compatibility-version was defaulting to 18 (VS 2013), which is a pain if your environment is pointing to version 19 (VS 2015) libraries. If cl.exe can be found, this patch uses its version number as the default instead. It re-uses the existing code to find the Visual Studio binaries folder and WinAPI methods to check its version. You can still explicitly specify a compatibility version on the command line. If you don't have cl.exe, this should be a no-op and you'll get the old default of 18. This affected the tests, which assumed that if you didn't specific a version, that it would default to 18, but this won't be true for all machines. So a couple test cases had to be eliminated and a couple others had to be tweaked to allow for various outputs. Addresses: https://llvm.org/bugs/show_bug.cgi?id=27215 Differential Revision: http://reviews.llvm.org/D20136 llvm-svn: 269515
2016-05-14 07:20:11 +08:00
// RUN: %clang_cl /c -### -fms-compatibility-version=18 -- %s 2>&1 | FileCheck -check-prefix=NoThreadSafeStatics %s
MS ABI: Implement driver-level support for thread-safe statics Decide whether or not to use thread-safe statics depending on whether or not we have an explicit request from the driver. If we don't have an explicit request, infer which behavior to use depending on the compatibility version we are targeting. N.B. CodeGen support is still ongoing. llvm-svn: 232906
2015-03-22 16:39:22 +08:00
// RUN: %clang_cl /Zc:threadSafeInit /Zc:threadSafeInit- /c -### -- %s 2>&1 | FileCheck -check-prefix=NoThreadSafeStatics %s
// NoThreadSafeStatics: "-fno-threadsafe-statics"
// RUN: %clang_cl /Zc:threadSafeInit /c -### -- %s 2>&1 | FileCheck -check-prefix=ThreadSafeStatics %s
// ThreadSafeStatics-NOT: "-fno-threadsafe-statics"
Add /Zc:DllexportInlines option to clang-cl Summary: This CL adds /Zc:DllexportInlines flag to clang-cl. When Zc:DllexportInlines- is specified, inline class member function is not exported if the function does not have local static variables. By not exporting inline function, code for those functions are not generated and that reduces both compile time and obj size. Also this flag does not import inline functions from dllimported class if the function does not have local static variables. On my 24C48T windows10 machine, build performance of chrome target in chromium repository is like below. These stats are come with 'target_cpu="x86" enable_nacl = false is_component_build=true dcheck_always_on=true` build config and applied * https://chromium-review.googlesource.com/c/chromium/src/+/1212379 * https://chromium-review.googlesource.com/c/v8/v8/+/1186017 Below stats were taken with this patch applied on https://github.com/llvm-project/llvm-project-20170507/commit/a05115cd4c57ff76b0f529e38118765b58ed7f2e | config | build time | speedup | build dir size | | with patch, PCH on, debug | 1h10m0s | x1.13 | 35.6GB | | without patch, PCH on, debug | 1h19m17s | | 49.0GB | | with patch, PCH off, debug | 1h15m45s | x1.16 | 33.7GB | | without patch, PCH off, debug | 1h28m10s | | 52.3GB | | with patch, PCH on, release | 1h13m13s | x1.22 | 26.2GB | | without patch, PCH on, release | 1h29m57s | | 37.5GB | | with patch, PCH off, release | 1h23m38s | x1.32 | 23.7GB | | without patch, PCH off, release | 1h50m50s | | 38.7GB | This patch reduced obj size and the number of exported symbols largely, that improved link time too. e.g. link time stats of blink_core.dll become like below | | cold disk cache | warm disk cache | | with patch, PCH on, debug | 71s | 30s | | without patch, PCH on, debug | 111s | 48s | This patch's implementation is based on Nico Weber's patch. I modified to support static local variable, added tests and took stats. Bug: https://bugs.llvm.org/show_bug.cgi?id=33628 Reviewers: hans, thakis, rnk, javed.absar Reviewed By: hans Subscribers: kristof.beyls, smeenai, dschuff, probinson, cfe-commits, eraman Differential Revision: https://reviews.llvm.org/D51340 llvm-svn: 346069
2018-11-03 14:45:00 +08:00
// RUN: %clang_cl /Zc:dllexportInlines- /c -### -- %s 2>&1 | FileCheck -check-prefix=NoDllExportInlines %s
// NoDllExportInlines: "-fno-dllexport-inlines"
// RUN: %clang_cl /Zc:dllexportInlines /c -### -- %s 2>&1 | FileCheck -check-prefix=DllExportInlines %s
// DllExportInlines-NOT: "-fno-dllexport-inlines"
[clang-cl] Add warning for /Zc:dllexportInlines- when the flag is used with /fallback Summary: This is followup of https://reviews.llvm.org/D51340 Reviewers: hans, thakis Reviewed By: hans Subscribers: cfe-commits, llvm-commits Differential Revision: https://reviews.llvm.org/D54298 llvm-svn: 346491
2018-11-09 21:25:45 +08:00
// RUN: %clang_cl /fallback /Zc:dllexportInlines- /c -### -- %s 2>&1 | FileCheck -check-prefix=DllExportInlinesFallback %s
[clang-cl] Do not allow using both /Zc:dllexportInlines- and /fallback flag Summary: /Zc:dllexportInlines with /fallback may cause unexpected linker error. It is better to disallow compile rather than warn for this combination. Reviewers: hans, thakis Reviewed By: hans Subscribers: cfe-commits, llvm-commits Differential Revision: https://reviews.llvm.org/D54426 llvm-svn: 346733
2018-11-13 12:14:09 +08:00
// DllExportInlinesFallback: error: option '/Zc:dllexportInlines-' is ABI-changing and not compatible with '/fallback'
Add /Zc:DllexportInlines option to clang-cl Summary: This CL adds /Zc:DllexportInlines flag to clang-cl. When Zc:DllexportInlines- is specified, inline class member function is not exported if the function does not have local static variables. By not exporting inline function, code for those functions are not generated and that reduces both compile time and obj size. Also this flag does not import inline functions from dllimported class if the function does not have local static variables. On my 24C48T windows10 machine, build performance of chrome target in chromium repository is like below. These stats are come with 'target_cpu="x86" enable_nacl = false is_component_build=true dcheck_always_on=true` build config and applied * https://chromium-review.googlesource.com/c/chromium/src/+/1212379 * https://chromium-review.googlesource.com/c/v8/v8/+/1186017 Below stats were taken with this patch applied on https://github.com/llvm-project/llvm-project-20170507/commit/a05115cd4c57ff76b0f529e38118765b58ed7f2e | config | build time | speedup | build dir size | | with patch, PCH on, debug | 1h10m0s | x1.13 | 35.6GB | | without patch, PCH on, debug | 1h19m17s | | 49.0GB | | with patch, PCH off, debug | 1h15m45s | x1.16 | 33.7GB | | without patch, PCH off, debug | 1h28m10s | | 52.3GB | | with patch, PCH on, release | 1h13m13s | x1.22 | 26.2GB | | without patch, PCH on, release | 1h29m57s | | 37.5GB | | with patch, PCH off, release | 1h23m38s | x1.32 | 23.7GB | | without patch, PCH off, release | 1h50m50s | | 38.7GB | This patch reduced obj size and the number of exported symbols largely, that improved link time too. e.g. link time stats of blink_core.dll become like below | | cold disk cache | warm disk cache | | with patch, PCH on, debug | 71s | 30s | | without patch, PCH on, debug | 111s | 48s | This patch's implementation is based on Nico Weber's patch. I modified to support static local variable, added tests and took stats. Bug: https://bugs.llvm.org/show_bug.cgi?id=33628 Reviewers: hans, thakis, rnk, javed.absar Reviewed By: hans Subscribers: kristof.beyls, smeenai, dschuff, probinson, cfe-commits, eraman Differential Revision: https://reviews.llvm.org/D51340 llvm-svn: 346069
2018-11-03 14:45:00 +08:00
Add -gcodeview and -gdwarf to control which type Clang emits Summary: By default, 'clang' emits dwarf and 'clang-cl' emits codeview. You can force emission of one or both by passing -gcodeview and -gdwarf to either driver. Reviewers: dblaikie, hans Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D11742 llvm-svn: 244097
2015-08-06 02:51:13 +08:00
// RUN: %clang_cl /Zi /c -### -- %s 2>&1 | FileCheck -check-prefix=Zi %s
// Zi: "-gcodeview"
[clang-cl] /Z7 now generates normal debug info, not just line info Previously LLVM could not process any debug info we produced, so it didn't make sense to spend time generating it. Now that it has primitive support for local variable info, it does make sense to generate normal debug info. llvm-svn: 260435
2016-02-11 05:28:38 +08:00
// Zi: "-debug-info-kind=limited"
Add -gcodeview and -gdwarf to control which type Clang emits Summary: By default, 'clang' emits dwarf and 'clang-cl' emits codeview. You can force emission of one or both by passing -gcodeview and -gdwarf to either driver. Reviewers: dblaikie, hans Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D11742 llvm-svn: 244097
2015-08-06 02:51:13 +08:00
// RUN: %clang_cl /Z7 /c -### -- %s 2>&1 | FileCheck -check-prefix=Z7 %s
// Z7: "-gcodeview"
[clang-cl] /Z7 now generates normal debug info, not just line info Previously LLVM could not process any debug info we produced, so it didn't make sense to spend time generating it. Now that it has primitive support for local variable info, it does make sense to generate normal debug info. llvm-svn: 260435
2016-02-11 05:28:38 +08:00
// Z7: "-debug-info-kind=limited"
Stop messing with the 'g' group of options in CompilerInvocation. With this change, most 'g' options are rejected by CompilerInvocation. They remain only as Driver options. The new way to request debug info from cc1 is with "-debug-info-kind={line-tables-only|limited|standalone}" and "-dwarf-version={2|3|4}". In the absence of a command-line option to specify Dwarf version, the Toolchain decides it, rather than placing Toolchain-specific logic in CompilerInvocation. Also fix a bug in the Windows compatibility argument parsing in which the "rightmost argument wins" principle failed. Differential Revision: http://reviews.llvm.org/D13221 llvm-svn: 249655
2015-10-08 12:24:12 +08:00
[clang-cl] Add support for /Zd MASM (ML.exe and ML64.exe) and older versions of MSVC (CL.exe) support a flag called /Zd which is more-or-less -gline-tables-only. It seems nicer to support this flag instead of exposing -gline-tables-only. llvm-svn: 274991
2016-07-10 05:49:16 +08:00
// RUN: %clang_cl /Zd /c -### -- %s 2>&1 | FileCheck -check-prefix=Z7GMLT %s
[clang-cl] Allow use of -gline-tables-only llvm-svn: 263816
2016-03-19 02:42:56 +08:00
// Z7GMLT: "-gcodeview"
// Z7GMLT: "-debug-info-kind=line-tables-only"
[clang-cl] Make -gline-tables-only imply -gcodeview It's surprising that you have to pass /Z7 in addition to -gcodeview to get debug info. The sanitizer runtime, for example, expects that if the compiler supports the -gline-tables-only flag, then it will emit debug info. llvm-svn: 278139
2016-08-10 01:23:56 +08:00
// RUN: %clang_cl -gline-tables-only /c -### -- %s 2>&1 | FileCheck -check-prefix=ZGMLT %s
// ZGMLT: "-gcodeview"
// ZGMLT: "-debug-info-kind=line-tables-only"
[clang-cl] Add support for /Brepro The /Brepro flag controls whether or not the compiler should embed timestamps into the object file. Object files which do not embed timestamps are not suitable for incremental linking but are suitable for hermetic build systems and staged self-hosts of clang. A normal clang spelling of this flag has been added, -mincremental-linker-compatible. llvm-svn: 256204
2015-12-22 06:09:34 +08:00
// RUN: %clang_cl /c -### -- %s 2>&1 | FileCheck -check-prefix=BreproDefault %s
// BreproDefault: "-mincremental-linker-compatible"
// RUN: %clang_cl /Brepro- /Brepro /c '-###' -- %s 2>&1 | FileCheck -check-prefix=Brepro %s
clang-cl: Make /Brepro actually work. /Brepro means we want reproducible builds, i.e. we _don't_ want the timestamp that's needed to be compatible with the incremental linker. https://reviews.llvm.org/D23805 llvm-svn: 279555
2016-08-24 03:32:02 +08:00
// Brepro-NOT: "-mincremental-linker-compatible"
[clang-cl] Add support for /Brepro The /Brepro flag controls whether or not the compiler should embed timestamps into the object file. Object files which do not embed timestamps are not suitable for incremental linking but are suitable for hermetic build systems and staged self-hosts of clang. A normal clang spelling of this flag has been added, -mincremental-linker-compatible. llvm-svn: 256204
2015-12-22 06:09:34 +08:00
// RUN: %clang_cl /Brepro /Brepro- /c '-###' -- %s 2>&1 | FileCheck -check-prefix=Brepro_ %s
clang-cl: Make /Brepro actually work. /Brepro means we want reproducible builds, i.e. we _don't_ want the timestamp that's needed to be compatible with the incremental linker. https://reviews.llvm.org/D23805 llvm-svn: 279555
2016-08-24 03:32:02 +08:00
// Brepro_: "-mincremental-linker-compatible"
[clang-cl] Add support for /Brepro The /Brepro flag controls whether or not the compiler should embed timestamps into the object file. Object files which do not embed timestamps are not suitable for incremental linking but are suitable for hermetic build systems and staged self-hosts of clang. A normal clang spelling of this flag has been added, -mincremental-linker-compatible. llvm-svn: 256204
2015-12-22 06:09:34 +08:00
Stop messing with the 'g' group of options in CompilerInvocation. With this change, most 'g' options are rejected by CompilerInvocation. They remain only as Driver options. The new way to request debug info from cc1 is with "-debug-info-kind={line-tables-only|limited|standalone}" and "-dwarf-version={2|3|4}". In the absence of a command-line option to specify Dwarf version, the Toolchain decides it, rather than placing Toolchain-specific logic in CompilerInvocation. Also fix a bug in the Windows compatibility argument parsing in which the "rightmost argument wins" principle failed. Differential Revision: http://reviews.llvm.org/D13221 llvm-svn: 249655
2015-10-08 12:24:12 +08:00
// This test was super sneaky: "/Z7" means "line-tables", but "-gdwarf" occurs
// later on the command line, so it should win. Interestingly the cc1 arguments
// came out right, but had wrong semantics, because an invariant assumed by
// CompilerInvocation was violated: it expects that at most one of {gdwarfN,
// line-tables-only} appear. If you assume that, then you can safely use
// Args.hasArg to test whether a boolean flag is present without caring
// where it appeared. And for this test, it appeared to the left of -gdwarf
// which made it "win". This test could not detect that bug.
Add -gcodeview and -gdwarf to control which type Clang emits Summary: By default, 'clang' emits dwarf and 'clang-cl' emits codeview. You can force emission of one or both by passing -gcodeview and -gdwarf to either driver. Reviewers: dblaikie, hans Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D11742 llvm-svn: 244097
2015-08-06 02:51:13 +08:00
// RUN: %clang_cl /Z7 -gdwarf /c -### -- %s 2>&1 | FileCheck -check-prefix=Z7_gdwarf %s
// Z7_gdwarf: "-gcodeview"
Stop messing with the 'g' group of options in CompilerInvocation. With this change, most 'g' options are rejected by CompilerInvocation. They remain only as Driver options. The new way to request debug info from cc1 is with "-debug-info-kind={line-tables-only|limited|standalone}" and "-dwarf-version={2|3|4}". In the absence of a command-line option to specify Dwarf version, the Toolchain decides it, rather than placing Toolchain-specific logic in CompilerInvocation. Also fix a bug in the Windows compatibility argument parsing in which the "rightmost argument wins" principle failed. Differential Revision: http://reviews.llvm.org/D13221 llvm-svn: 249655
2015-10-08 12:24:12 +08:00
// Z7_gdwarf: "-debug-info-kind=limited"
// Z7_gdwarf: "-dwarf-version=4"
Add -gcodeview and -gdwarf to control which type Clang emits Summary: By default, 'clang' emits dwarf and 'clang-cl' emits codeview. You can force emission of one or both by passing -gcodeview and -gdwarf to either driver. Reviewers: dblaikie, hans Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D11742 llvm-svn: 244097
2015-08-06 02:51:13 +08:00
[clang-cl] Enable C++14 when targeting 2015 compatibility llvm-svn: 237553
2015-05-18 12:49:30 +08:00
// RUN: %clang_cl -fmsc-version=1800 -TP -### -- %s 2>&1 | FileCheck -check-prefix=CXX11 %s
// CXX11: -std=c++11
// RUN: %clang_cl -fmsc-version=1900 -TP -### -- %s 2>&1 | FileCheck -check-prefix=CXX14 %s
// CXX14: -std=c++14
[clang-cl] Implement support for /std /std: supports two arguments, c++14 and c++latest. Currently, c++latest maps to c++1z but this might change down the road. llvm-svn: 273841
2016-06-27 10:32:12 +08:00
// RUN: %clang_cl -fmsc-version=1900 -TP -std:c++14 -### -- %s 2>&1 | FileCheck -check-prefix=STDCXX14 %s
// STDCXX14: -std=c++14
[driver] [cl] Add/fix c++17/c++latest Patch by: daxpedda Differential Revision: https://reviews.llvm.org/D38123 llvm-svn: 315864
2017-10-16 01:27:58 +08:00
// RUN: %clang_cl -fmsc-version=1900 -TP -std:c++17 -### -- %s 2>&1 | FileCheck -check-prefix=STDCXX17 %s
Fix test case regresstion from rL315864 The patch should have been checking against STDCXX17 not STDCXX14. llvm-svn: 315868
2017-10-16 02:01:28 +08:00
// STDCXX17: -std=c++17
[driver] [cl] Add/fix c++17/c++latest Patch by: daxpedda Differential Revision: https://reviews.llvm.org/D38123 llvm-svn: 315864
2017-10-16 01:27:58 +08:00
[clang-cl] Implement support for /std /std: supports two arguments, c++14 and c++latest. Currently, c++latest maps to c++1z but this might change down the road. llvm-svn: 273841
2016-06-27 10:32:12 +08:00
// RUN: %clang_cl -fmsc-version=1900 -TP -std:c++latest -### -- %s 2>&1 | FileCheck -check-prefix=STDCXXLATEST %s
[driver] [cl] Add/fix c++17/c++latest Patch by: daxpedda Differential Revision: https://reviews.llvm.org/D38123 llvm-svn: 315864
2017-10-16 01:27:58 +08:00
// STDCXXLATEST: -std=c++2a
[clang-cl] Implement support for /std /std: supports two arguments, c++14 and c++latest. Currently, c++latest maps to c++1z but this might change down the road. llvm-svn: 273841
2016-06-27 10:32:12 +08:00
[clang-cl] Add support for CL and _CL_ environment variables cl uses 'CL' and '_CL_' to prepend and append command line options to the given argument vector. There is an additional quirk whereby '#' is transformed into '='. Differential Revision: http://reviews.llvm.org/D11896 llvm-svn: 244473
2015-08-11 02:16:32 +08:00
// RUN: env CL="/Gy" %clang_cl -### -- %s 2>&1 | FileCheck -check-prefix=ENV-CL %s
// ENV-CL: "-ffunction-sections"
// RUN: env CL="/Gy" _CL_="/Gy- -- %s" %clang_cl -### 2>&1 | FileCheck -check-prefix=ENV-_CL_ %s
// ENV-_CL_-NOT: "-ffunction-sections"
[clang-cl] Check that we are in clang cl mode before enabling support for the CL environment variable. Checking for the type of the command line tokenizer should not be the criteria to enable support for the CL environment variable, this change checks that we are in clang-cl mode instead. Differential Revision: https://reviews.llvm.org/D23503 llvm-svn: 280702
2016-09-06 18:48:27 +08:00
// RUN: env CL="%s" _CL_="%s" not %clang --rsp-quoting=windows -c
enable -flto=thin in clang-cl Summary: This enables LTO to be used with the clang-cl frontend. Reviewers: rnk, hans Reviewed By: hans Subscribers: pcc, cfe-commits, mehdi_amini, Prazek Differential Revision: https://reviews.llvm.org/D30239 llvm-svn: 296373
2017-02-28 03:40:19 +08:00
// RUN: %clang_cl -### /c -flto -- %s 2>&1 | FileCheck -check-prefix=LTO %s
// LTO: -flto
// RUN: %clang_cl -### /c -flto=thin -- %s 2>&1 | FileCheck -check-prefix=LTO-THIN %s
// LTO-THIN: -flto=thin
// RUN: %clang_cl -### -Fe%t.exe -entry:main -flto -- %s 2>&1 | FileCheck -check-prefix=LTO-WITHOUT-LLD %s
// LTO-WITHOUT-LLD: LTO requires -fuse-ld=lld
clang-cl: Support /guard:cf,nochecks This extension emits the guard cf table without inserting the instrumentation. Currently that's what clang-cl does with /guard:cf anyway, but this allows a user to request that explicitly. Differential Revision: https://reviews.llvm.org/D50513 llvm-svn: 339420
2018-08-10 17:49:21 +08:00
// RUN: %clang_cl -### -- %s 2>&1 | FileCheck -check-prefix=NOCFGUARD %s
// RUN: %clang_cl /guard:cf- -### -- %s 2>&1 | FileCheck -check-prefix=NOCFGUARD %s
cl-options.c: Fix negative -cfguard check llvm-svn: 342470
2018-09-18 21:07:55 +08:00
// NOCFGUARD-NOT: -cfguard
clang-cl: Support /guard:cf,nochecks This extension emits the guard cf table without inserting the instrumentation. Currently that's what clang-cl does with /guard:cf anyway, but this allows a user to request that explicitly. Differential Revision: https://reviews.llvm.org/D50513 llvm-svn: 339420
2018-08-10 17:49:21 +08:00
// RUN: %clang_cl /guard:cf -### -- %s 2>&1 | FileCheck -check-prefix=CFGUARD %s
// RUN: %clang_cl /guard:cf,nochecks -### -- %s 2>&1 | FileCheck -check-prefix=CFGUARD %s
// RUN: %clang_cl /guard:nochecks -### -- %s 2>&1 | FileCheck -check-prefix=CFGUARD %s
// CFGUARD: -cfguard
// RUN: %clang_cl /guard:foo -### -- %s 2>&1 | FileCheck -check-prefix=CFGUARDINVALID %s
// CFGUARDINVALID: invalid value 'foo' in '/guard:'
clang-cl: make sure we still parse -fms-version= after r213119 The CoreOption flag got lost in the changes. llvm-svn: 213164
2014-07-17 00:03:56 +08:00
// Accept "core" clang options.
clang-cl: support -fmacro-backtrace-limit Also fix the test for "core options" to actually fail in case an option isn't supported. llvm-svn: 234684
2015-04-11 19:44:44 +08:00
// (/Zs is for syntax-only, -Werror makes it fail hard on unknown options)
clang-cl: expand test coverage for "core" options llvm-svn: 213170
2014-07-17 00:29:00 +08:00
// RUN: %clang_cl \
// RUN: --driver-mode=cl \
[clang-cl] Expose -fblocks and -fno-builtin as driver flags Users have requested them. Helps with PR36427. llvm-svn: 337746
2018-07-24 05:29:43 +08:00
// RUN: -fblocks \
clang-cl: accept -fcrash-diagnostics-dir= llvm-svn: 339424
2018-08-10 19:40:50 +08:00
// RUN: -fcrash-diagnostics-dir=/foo \
clang-cl: Expose -fno-crash-diagnostics (PR38574) llvm-svn: 340023
2018-08-17 21:37:57 +08:00
// RUN: -fno-crash-diagnostics \
[clang-cl] Expose -fblocks and -fno-builtin as driver flags Users have requested them. Helps with PR36427. llvm-svn: 337746
2018-07-24 05:29:43 +08:00
// RUN: -fno-blocks \
// RUN: -fbuiltin \
// RUN: -fno-builtin \
// RUN: -fno-builtin-strcpy \
clang-cl: support -fno-color-diagnostics (PR23109) Patch by Bernard Solomon, tests by me. llvm-svn: 234685
2015-04-11 20:27:56 +08:00
// RUN: -fcolor-diagnostics \
// RUN: -fno-color-diagnostics \
add test for r332053 llvm-svn: 333423
2018-05-29 22:48:30 +08:00
// RUN: -fcoverage-mapping \
// RUN: -fno-coverage-mapping \
clang-cl: Expose -f[no-]diagnostics-color If we have -f[no-]color-diagnostics, we might as well have these too. llvm-svn: 234702
2015-04-12 15:12:19 +08:00
// RUN: -fdiagnostics-color \
// RUN: -fno-diagnostics-color \
Promote -fdebug-compilation-dir from a cc1 flag to clang and clang-cl driver flags The flag is useful when wanting to create .o files that are independent from the absolute path to the build directory. -fdebug-prefix-map= can be used to the same effect, but it requires putting the absolute path to the build directory on the build command line, so it still requires the build command line to be dependent on the absolute path of the build directory. With this flag, "-fdebug-compilation-dir ." makes it so that both debug info and the compile command itself are independent of the absolute path of the build directory, which is good for build determinism (in the sense that the build is independent of which directory it happens in) and for caching compile results. (The tradeoff is that the debugger needs explicit configuration to know the build directory. See also http://dwarfstd.org/ShowIssue.php?issue=171130.2) Differential Revision: https://reviews.llvm.org/D63387 llvm-svn: 363548
2019-06-17 20:10:40 +08:00
// RUN: -fdebug-compilation-dir . \
Expose -fdiagnostics-parseable-fixits to clang-cl Patch by Daniel Cheng! Differential Revision: http://reviews.llvm.org/D9175 llvm-svn: 235456
2015-04-22 07:12:03 +08:00
// RUN: -fdiagnostics-parseable-fixits \
Add support for -fdiagnostics-absolute-paths: printing absolute paths in diagnostics Differential Revision: https://reviews.llvm.org/D23816 llvm-svn: 279827
2016-08-26 23:45:36 +08:00
// RUN: -fdiagnostics-absolute-paths \
clang-cl: expand test coverage for "core" options llvm-svn: 213170
2014-07-17 00:29:00 +08:00
// RUN: -ferror-limit=10 \
clang-cl: make sure we still parse -fms-version= after r213119 The CoreOption flag got lost in the changes. llvm-svn: 213164
2014-07-17 00:03:56 +08:00
// RUN: -fmsc-version=1800 \
clang-cl: expand test coverage for "core" options llvm-svn: 213170
2014-07-17 00:29:00 +08:00
// RUN: -fno-strict-aliasing \
// RUN: -fstrict-aliasing \
clang-cl: support -fsyntax-only (PR23197) This might help running Clang tooling (which appends this option) with clang-cl command-lines. llvm-svn: 234990
2015-04-15 18:02:21 +08:00
// RUN: -fsyntax-only \
Expose -f[no]ms-{compatibility,extensions} in clang-cl (PR25114) These are enabled by default in clang-cl, because the whole idea is that it should work like cl.exe, but I suppose it can make sense to disable them if someone wants to compile code in a more strict mode. llvm-svn: 249775
2015-10-09 07:13:28 +08:00
// RUN: -fms-compatibility \
// RUN: -fno-ms-compatibility \
// RUN: -fms-extensions \
// RUN: -fno-ms-extensions \
Address review comments on r290392: - Don't break using '-mllvm -disable-llvm-optzns' (yet). - Don't add support for '-mllvm -disable-llvm-passes'. This is important for LLVM 4 as we haven't yet really told folks this is coming. I'll add release notes about this. I've also added some explicit testing of this so its more obvious what is happening here. llvm-svn: 291850
2017-01-13 06:40:13 +08:00
// RUN: -Xclang -disable-llvm-passes \
[clang-cl] Accept the joined equals version of -resource-dir= lib/Tooling injects this argument without regard for what driver syntax is in use. llvm-svn: 281550
2016-09-15 06:31:24 +08:00
// RUN: -resource-dir asdf \
// RUN: -resource-dir=asdf \
clang-cl: support -fmacro-backtrace-limit Also fix the test for "core options" to actually fail in case an option isn't supported. llvm-svn: 234684
2015-04-11 19:44:44 +08:00
// RUN: -Wunused-variable \
// RUN: -fmacro-backtrace-limit=0 \
Make -fstandalone-debug and -flimit-debug-info available in clang-cl Our limited debug info optimizations are breaking down at DLL boundaries, so we're going to evaluate the size impact of these settings, and possibly change the default. Users should be able to override our settings, though. llvm-svn: 281056
2016-09-10 00:42:50 +08:00
// RUN: -fstandalone-debug \
// RUN: -flimit-debug-info \
clang-cl: Expose the -flto option We could hook up /GL as an alias for -flto, but that might be confusing, as clang-cl in that mode would not be drop-in compatible with cl.exe /GL, as it requires the linker to be lld. Exposing -flto seems like a less confusing way to expose this functionality. llvm-svn: 283255
2016-10-05 05:00:57 +08:00
// RUN: -flto \
clang-cl: Expose -fmerge-all-constants Now that constant merging is off by default, we'd like a way to enable it on Windows. llvm-svn: 331214
2018-05-01 03:04:04 +08:00
// RUN: -fmerge-all-constants \
clang-cl: Expose -no-canonical-prefixes -no-canonical-prefixes is a weird flag: In gcc, it controls whether realpath() is called on the path of the driver binary. It's needed to support some usecases where gcc is symlinked to, see https://gcc.gnu.org/ml/gcc/2011-01/msg00429.html for some background. In clang, the resource dir is found relative to the compiler binary, and without -no-canonical-prefixes that's an absolute path. For clang, the main use case for -no-canonical-prefixes is to make the -resource-dir path added by the driver relative instead of absolute. Making it relative seems like the better default, but since neither clang not gcc have -canonical-prefixes without no- which makes changing the default tricky, and since some symlink behaviors do depend on the realpath() call at least for gcc, just expose -no-canonical-prefixes in clang-cl mode. Alternatively we could default to no-canonical-prefix-mode for clang-cl since it's less likely to be used in symlinked scenarios, but since you already need to about -no-canonical-prefixes for the non-clang-cl bits of your build, not hooking this of driver mode seems better to me. https://reviews.llvm.org/D47480 llvm-svn: 333761
2018-06-01 22:59:57 +08:00
// RUN: -no-canonical-prefixes \
[clang-cl] Enable -march option This change allows usage of -march when using the clang-cl driver. This is similar to MSVC's /arch; however -march can target precisely all supported CPUs, while /arch has a more restricted set. Differential Revision: https://reviews.llvm.org/D51806 llvm-svn: 341847
2018-09-11 01:54:32 +08:00
// RUN: -march=skylake \
[clang-cl] Whitelist -fbracket-depth=123 in clang-cl Users apparently need it when expanding large quantities of macros. Fixes PR38685 llvm-svn: 354626
2019-02-22 05:53:12 +08:00
// RUN: -fbracket-depth=123 \
clang-cl: Expose -fprofile-generate and -fcs-profile-generate (PR41252) llvm-svn: 357255
2019-03-29 22:03:34 +08:00
// RUN: -fprofile-generate \
// RUN: -fprofile-generate=dir \
// RUN: -fno-profile-generate \
// RUN: -fno-profile-instr-generate \
// RUN: -fno-profile-instr-use \
// RUN: -fcs-profile-generate \
// RUN: -fcs-profile-generate=dir \
ftime-trace as a CoreOption Differential Revision: https://reviews.llvm.org/D61945 llvm-svn: 360907
2019-05-16 23:14:01 +08:00
// RUN: -ftime-trace \
clang-cl: Expose --version. This is for consistency with lld-link, see https://reviews.llvm.org/D38972 Also give --version a help text so it shows up in --help / /? output (for both clang-cl and regular clang). llvm-svn: 316335
2017-10-23 23:54:44 +08:00
// RUN: --version \
clang-cl: support -fmacro-backtrace-limit Also fix the test for "core options" to actually fail in case an option isn't supported. llvm-svn: 234684
2015-04-11 19:44:44 +08:00
// RUN: -Werror /Zs -- %s 2>&1
clang-cl: make sure we still parse -fms-version= after r213119 The CoreOption flag got lost in the changes. llvm-svn: 213164
2014-07-17 00:03:56 +08:00
clang-cl: Add "/clang:" pass-through arg support. The clang-cl driver disables access to command line options outside of the "Core" and "CLOption" sets of command line arguments. This filtering makes it impossible to pass arguments that are interpreted by the clang driver and not by either 'cc1' (the frontend) or one of the other tools invoked by the driver. An example driver-level flag is the '-fno-slp-vectorize' flag, which is processed by the driver in Clang::ConstructJob and used to set the cc1 flag "-vectorize-slp". There is no negative cc1 flag or -mllvm flag, so it is not currently possible to disable the SLP vectorizer from the clang-cl driver. This change introduces the "/clang:" argument that is available when the driver mode is set to CL compatibility. This option works similarly to the "-Xclang" option, except that the option values are processed by the clang driver rather than by 'cc1'. An example usage is: clang-cl /clang:-fno-slp-vectorize /O2 test.c Another example shows how "/clang:" can be used to pass a flag where there is a conflict between a clang-cl compat option and an overlapping clang driver option: clang-cl /MD /clang:-MD /clang:-MF /clang:test_dep_file.dep test.c In the previous example, the unprefixed /MD selects the DLL version of the msvc CRT, while the prefixed -MD flag and the -MF flags are used to create a make dependency file for included headers. One note about flag ordering: the /clang: flags are concatenated to the end of the argument list, so in cases where the last flag wins, the /clang: flags will be chosen regardless of their order relative to other flags on the driver command line. Patch by Neeraj K. Singh! Differential revision: https://reviews.llvm.org/D53457 llvm-svn: 346393
2018-11-08 19:27:04 +08:00
// Accept clang options under the /clang: flag.
// The first test case ensures that the SLP vectorizer is on by default and that
// it's being turned off by the /clang:-fno-slp-vectorize flag.
// RUN: %clang_cl -O2 -### -- %s 2>&1 | FileCheck -check-prefix=NOCLANG %s
// NOCLANG: "--dependent-lib=libcmt"
// NOCLANG-SAME: "-vectorize-slp"
// NOCLANG-NOT: "--dependent-lib=msvcrt"
// RUN: %clang_cl -O2 -MD /clang:-fno-slp-vectorize /clang:-MD /clang:-MF /clang:my_dependency_file.dep -### -- %s 2>&1 | FileCheck -check-prefix=CLANG %s
// CLANG: "--dependent-lib=msvcrt"
// CLANG-SAME: "-dependency-file" "my_dependency_file.dep"
// CLANG-NOT: "--dependent-lib=libcmt"
// CLANG-NOT: "-vectorize-slp"
clang-cl: Expose the -m32 and -m64 command-line options And add a test to check that they work. llvm-svn: 192402
2013-10-11 06:36:20 +08:00
clang-cl: ignore compile-only options in link-only invocations. Previously we would warn about unused arguments such as /MD when linking. Clang already has logic to ignore compile-only options, e.g. for -D and -U. This patch extends that to include clang-cl's compile-only options too. Also, some clang-cl options should always be ignored. Doing this earlier means they get ignored both for compilation and link-only invocations. llvm-svn: 190825
2013-09-17 08:03:41 +08:00
void f() { }