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/integrated-as.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

61 lines
3.3 KiB
ArmAsm
Raw Normal View History

test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s 2>&1 | FileCheck %s
Add tests for a corner case of when to relax all instructions: We don't want to relax all instructions in $ clang -c test.s since most users don't pass -O when using the driver to assemble. On the other hand, -save-temps should not change the output unnecessary, so in $ clang -c test.c -save-temps we should relax all instructions. llvm-svn: 169815
2012-12-11 13:52:24 +08:00
// CHECK: cc1as
// CHECK-NOT: -relax-all
Don't forward all assembler arguments untouched to -cc1as Use the same filtering for assembly arguments to -cc1as as we do for -cc1, this allows a consistent (& more useful) diagnostic experience for users (rather than getting an error from -cc1as (which a user shouldn't really be thinking about) about --foo, they get an error from clang about --foo in -Wa,) I'm sort of surprised by the separation of -cc1as & the separate argument handling, etc, but at least this removes a little bit of the duplication. llvm-svn: 187156
2013-07-26 05:19:01 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as -Wa,-L %s 2>&1 | FileCheck --check-prefix=OPT_L %s
Fix up fallout from r187156. The previous change caused the driver to translate -Wa,-L to the -msave-temp-labels option for cc1as, but cc1as did not accept that option. This patch follows the same approach used for similar options (-relax-all, -noexecstack) in the previous patch. llvm-svn: 191458
2013-09-27 05:00:51 +08:00
// OPT_L: msave-temp-labels
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// Test that -I params in -Wa, and -Xassembler args are passed to integrated assembler
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-I,foo_dir 2>&1 | FileCheck --check-prefix=WA_INCLUDE1 %s
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// WA_INCLUDE1: cc1as
// WA_INCLUDE1: "-I" "foo_dir"
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-Ifoo_dir 2>&1 | FileCheck --check-prefix=WA_INCLUDE2 %s
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// WA_INCLUDE2: cc1as
// WA_INCLUDE2: "-Ifoo_dir"
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-I -Wa,foo_dir 2>&1 | FileCheck --check-prefix=WA_INCLUDE3 %s
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// WA_INCLUDE3: cc1as
// WA_INCLUDE3: "-I" "foo_dir"
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Xassembler -I -Xassembler foo_dir 2>&1 | FileCheck --check-prefix=XA_INCLUDE1 %s
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// XA_INCLUDE1: cc1as
// XA_INCLUDE1: "-I" "foo_dir"
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Xassembler -Ifoo_dir 2>&1 | FileCheck --check-prefix=XA_INCLUDE2 %s
Pass -Wa,-I and -Xassembler -I args to integrated assembler This patch adds -I to the arguments that are passed to the integrated assembler from -Wa, and -Xassembler args. llvm-svn: 194743
2013-11-15 06:52:58 +08:00
// XA_INCLUDE2: cc1as
// XA_INCLUDE2: "-Ifoo_dir"
Driver: Stub -Wa,-compress-debug-sections support for integrated-as with a suppressable warning llvm-svn: 199454
2014-01-17 11:17:40 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -gdwarf-4 -gdwarf-2 2>&1 | FileCheck --check-prefix=DWARF2 %s
Switch to using -debug-info-kind=constructor as default (from =limited) Summary: -debug-info-kind=constructor reduces the amount of class debug info that is emitted; this patch switches to using this as the default. Constructor homing emits the complete type info for a class only when the constructor is emitted, so it is expected that there will be some classes that are not defined in the debug info anymore because they are never constructed, and we shouldn't need debug info for these classes. I compared the PDB files for clang, and there are 273 class types that are defined with `=limited` but not with `=constructor` (out of ~60,000 total class types). We've looked at a number of the types that are no longer defined with =constructor. The vast majority of cases are something like class A is used as a parameter in a member function of some other class B, which is emitted. But the function that uses class A is never called, and class A is never constructed, and therefore isn't emitted in the debug info. Bug: https://bugs.llvm.org/show_bug.cgi?id=46537 Subscribers: aprantl, cfe-commits, lldb-commits Tags: #clang, #lldb Differential Revision: https://reviews.llvm.org/D79147
2020-04-30 07:21:05 +08:00
// DWARF2: "-debug-info-kind=constructor" "-dwarf-version=2"
Pass -gdwarf-N options to integrated assembler llvm-svn: 209124
2014-05-19 21:39:13 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -gdwarf-3 2>&1 | FileCheck --check-prefix=DWARF3 %s
Switch to using -debug-info-kind=constructor as default (from =limited) Summary: -debug-info-kind=constructor reduces the amount of class debug info that is emitted; this patch switches to using this as the default. Constructor homing emits the complete type info for a class only when the constructor is emitted, so it is expected that there will be some classes that are not defined in the debug info anymore because they are never constructed, and we shouldn't need debug info for these classes. I compared the PDB files for clang, and there are 273 class types that are defined with `=limited` but not with `=constructor` (out of ~60,000 total class types). We've looked at a number of the types that are no longer defined with =constructor. The vast majority of cases are something like class A is used as a parameter in a member function of some other class B, which is emitted. But the function that uses class A is never called, and class A is never constructed, and therefore isn't emitted in the debug info. Bug: https://bugs.llvm.org/show_bug.cgi?id=46537 Subscribers: aprantl, cfe-commits, lldb-commits Tags: #clang, #lldb Differential Revision: https://reviews.llvm.org/D79147
2020-04-30 07:21:05 +08:00
// DWARF3: "-debug-info-kind=constructor" "-dwarf-version=3"
Pass -gdwarf-N options to integrated assembler llvm-svn: 209124
2014-05-19 21:39:13 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -gdwarf-4 2>&1 | FileCheck --check-prefix=DWARF4 %s
Switch to using -debug-info-kind=constructor as default (from =limited) Summary: -debug-info-kind=constructor reduces the amount of class debug info that is emitted; this patch switches to using this as the default. Constructor homing emits the complete type info for a class only when the constructor is emitted, so it is expected that there will be some classes that are not defined in the debug info anymore because they are never constructed, and we shouldn't need debug info for these classes. I compared the PDB files for clang, and there are 273 class types that are defined with `=limited` but not with `=constructor` (out of ~60,000 total class types). We've looked at a number of the types that are no longer defined with =constructor. The vast majority of cases are something like class A is used as a parameter in a member function of some other class B, which is emitted. But the function that uses class A is never called, and class A is never constructed, and therefore isn't emitted in the debug info. Bug: https://bugs.llvm.org/show_bug.cgi?id=46537 Subscribers: aprantl, cfe-commits, lldb-commits Tags: #clang, #lldb Differential Revision: https://reviews.llvm.org/D79147
2020-04-30 07:21:05 +08:00
// DWARF4: "-debug-info-kind=constructor" "-dwarf-version=4"
Pass -gdwarf-N options to integrated assembler llvm-svn: 209124
2014-05-19 21:39:13 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Xassembler -gdwarf-2 2>&1 | FileCheck --check-prefix=DWARF2XASSEMBLER %s
Switch to using -debug-info-kind=constructor as default (from =limited) Summary: -debug-info-kind=constructor reduces the amount of class debug info that is emitted; this patch switches to using this as the default. Constructor homing emits the complete type info for a class only when the constructor is emitted, so it is expected that there will be some classes that are not defined in the debug info anymore because they are never constructed, and we shouldn't need debug info for these classes. I compared the PDB files for clang, and there are 273 class types that are defined with `=limited` but not with `=constructor` (out of ~60,000 total class types). We've looked at a number of the types that are no longer defined with =constructor. The vast majority of cases are something like class A is used as a parameter in a member function of some other class B, which is emitted. But the function that uses class A is never called, and class A is never constructed, and therefore isn't emitted in the debug info. Bug: https://bugs.llvm.org/show_bug.cgi?id=46537 Subscribers: aprantl, cfe-commits, lldb-commits Tags: #clang, #lldb Differential Revision: https://reviews.llvm.org/D79147
2020-04-30 07:21:05 +08:00
// DWARF2XASSEMBLER: "-debug-info-kind=constructor" "-dwarf-version=2"
Pass -gdwarf-N options to integrated assembler llvm-svn: 209124
2014-05-19 21:39:13 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-gdwarf-2 2>&1 | FileCheck --check-prefix=DWARF2WA %s
Switch to using -debug-info-kind=constructor as default (from =limited) Summary: -debug-info-kind=constructor reduces the amount of class debug info that is emitted; this patch switches to using this as the default. Constructor homing emits the complete type info for a class only when the constructor is emitted, so it is expected that there will be some classes that are not defined in the debug info anymore because they are never constructed, and we shouldn't need debug info for these classes. I compared the PDB files for clang, and there are 273 class types that are defined with `=limited` but not with `=constructor` (out of ~60,000 total class types). We've looked at a number of the types that are no longer defined with =constructor. The vast majority of cases are something like class A is used as a parameter in a member function of some other class B, which is emitted. But the function that uses class A is never called, and class A is never constructed, and therefore isn't emitted in the debug info. Bug: https://bugs.llvm.org/show_bug.cgi?id=46537 Subscribers: aprantl, cfe-commits, lldb-commits Tags: #clang, #lldb Differential Revision: https://reviews.llvm.org/D79147
2020-04-30 07:21:05 +08:00
// DWARF2WA: "-debug-info-kind=constructor" "-dwarf-version=2"
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
// A dwarf version number that driver can't parse is just stuffed in.
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-gdwarf-huh 2>&1 | FileCheck --check-prefix=BOGODWARF %s
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
// BOGODWARF: "-gdwarf-huh"
Driver: Pass -I options to cc1as for .include search paths. llvm-svn: 240432
2015-06-24 02:20:13 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -x assembler -c -integrated-as %s -I myincludedir 2>&1 | FileCheck --check-prefix=INCLUDEPATH %s
Driver: Pass -I options to cc1as for .include search paths. llvm-svn: 240432
2015-06-24 02:20:13 +08:00
// INCLUDEPATH: "-I" "myincludedir"
Properly pass through the PIC mode to the integrated assembler when doing assembly-only, and unify the Driver's PIC argument parsing. On a few architectures, parsing of assembly files annoyingly depends on whether PIC is enabled or not. This was handled for external 'as' already (passing -KPIC), but was missed for calls to the standalone internal assembler. The integrated-as.s test needed to be modified to not expect -fsanitize=address to be unused, as now fsanitize *IS* used for assembly, since -fsanitize=memory can sometimes imply -fPIE, which the assembler needs to know (gack!!). Differential Revision: http://reviews.llvm.org/D11845 llvm-svn: 245447
2015-08-19 23:12:02 +08:00
test: add explicit triples to the invocation llvm-svn: 290534
2016-12-26 12:00:54 +08:00
// RUN: %clang -### -target x86_64--- -x assembler -c -fPIC -integrated-as %s 2>&1 | FileCheck --check-prefix=PIC %s
Properly pass through the PIC mode to the integrated assembler when doing assembly-only, and unify the Driver's PIC argument parsing. On a few architectures, parsing of assembly files annoyingly depends on whether PIC is enabled or not. This was handled for external 'as' already (passing -KPIC), but was missed for calls to the standalone internal assembler. The integrated-as.s test needed to be modified to not expect -fsanitize=address to be unused, as now fsanitize *IS* used for assembly, since -fsanitize=memory can sometimes imply -fPIE, which the assembler needs to know (gack!!). Differential Revision: http://reviews.llvm.org/D11845 llvm-svn: 245447
2015-08-19 23:12:02 +08:00
// PIC: "-mrelocation-model" "pic"
Allow forwarding -fdebug-compilation-dir to cc1as The flag -fdebug-compilation-dir is useful to make generated .o files independent of the path of the build directory, without making the compile command-line dependent on the path of the build directory, like -fdebug-prefix-map requires. This change makes it so that the driver can forward the flag to -cc1as, like it already can for -cc1. We might want to consider making -fdebug-compilation-dir a driver flag in a follow-up. (Since -fdebug-compilation-dir defaults to PWD, it's already possible to get this effect by setting PWD, but explicit compiler flags are better than env vars, because e.g. ninja tracks command lines and reruns commands that change.) Somewhat related to PR14625. Differential Revision: https://reviews.llvm.org/D55377 llvm-svn: 348515
2018-12-07 02:50:39 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-fdebug-compilation-dir,. 2>&1 | FileCheck --check-prefix=WA_DEBUGDIR %s
driver: Allow -fdebug-compilation-dir=foo in joined form. All 130+ f_Group flags that take an argument allow it after a '=', except for fdebug-complation-dir. Add a Joined<> alias so that it behaves consistently with all the other f_Group flags. (Keep the old Separate flag for backwards compat.)
2020-01-11 08:18:11 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Wa,-fdebug-compilation-dir=. 2>&1 | FileCheck --check-prefix=WA_DEBUGDIR %s
Allow forwarding -fdebug-compilation-dir to cc1as The flag -fdebug-compilation-dir is useful to make generated .o files independent of the path of the build directory, without making the compile command-line dependent on the path of the build directory, like -fdebug-prefix-map requires. This change makes it so that the driver can forward the flag to -cc1as, like it already can for -cc1. We might want to consider making -fdebug-compilation-dir a driver flag in a follow-up. (Since -fdebug-compilation-dir defaults to PWD, it's already possible to get this effect by setting PWD, but explicit compiler flags are better than env vars, because e.g. ninja tracks command lines and reruns commands that change.) Somewhat related to PR14625. Differential Revision: https://reviews.llvm.org/D55377 llvm-svn: 348515
2018-12-07 02:50:39 +08:00
// WA_DEBUGDIR: "-fdebug-compilation-dir" "."
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Xassembler -fdebug-compilation-dir -Xassembler . 2>&1 | FileCheck --check-prefix=XA_DEBUGDIR %s
driver: Allow -fdebug-compilation-dir=foo in joined form. All 130+ f_Group flags that take an argument allow it after a '=', except for fdebug-complation-dir. Add a Joined<> alias so that it behaves consistently with all the other f_Group flags. (Keep the old Separate flag for backwards compat.)
2020-01-11 08:18:11 +08:00
// RUN: %clang -### -target x86_64--- -c -integrated-as %s -Xassembler -fdebug-compilation-dir=. 2>&1 | FileCheck --check-prefix=XA_DEBUGDIR %s
Allow forwarding -fdebug-compilation-dir to cc1as The flag -fdebug-compilation-dir is useful to make generated .o files independent of the path of the build directory, without making the compile command-line dependent on the path of the build directory, like -fdebug-prefix-map requires. This change makes it so that the driver can forward the flag to -cc1as, like it already can for -cc1. We might want to consider making -fdebug-compilation-dir a driver flag in a follow-up. (Since -fdebug-compilation-dir defaults to PWD, it's already possible to get this effect by setting PWD, but explicit compiler flags are better than env vars, because e.g. ninja tracks command lines and reruns commands that change.) Somewhat related to PR14625. Differential Revision: https://reviews.llvm.org/D55377 llvm-svn: 348515
2018-12-07 02:50:39 +08:00
// XA_DEBUGDIR: "-fdebug-compilation-dir" "."