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/mips-abi.c

190 lines
7.3 KiB
C
Raw Normal View History

[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// Check passing Mips ABI options to the backend.
//
[mips] Add missing mips-registered-target to mips test. llvm-svn: 310715
2017-08-11 23:23:23 +08:00
// REQUIRES: mips-registered-target
//
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
// RUN: %clang -target mips-linux-gnu -### -c %s 2>&1 \
[mips] Defer validity check for CPU/ABI pairs and improve error message for invalid cases. Summary: The validity of ABI/CPU pairs is no longer checked on the fly but is instead checked after initialization. As a result, invalid CPU/ABI pairs can be reported as being known but invalid instead of being unknown. For example, we now emit: error: ABI 'n32' is not supported on CPU 'mips32r2' instead of: error: unknown target ABI 'n64' Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21023 llvm-svn: 272645
2016-06-14 16:58:50 +08:00
// RUN: | FileCheck -check-prefix=MIPS32R2-O32 %s
// RUN: %clang -target mips64-linux-gnu -mips32r2 -mabi=32 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS32R2-O32 %s
// MIPS32R2-O32: "-target-cpu" "mips32r2"
// MIPS32R2-O32: "-target-abi" "o32"
//
// FIXME: This is a valid combination of options but we reject it at the moment
// because the backend can't handle it.
// RUN: not %clang -target mips-linux-gnu -c %s \
// RUN: -march=mips64r2 -mabi=32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R2-O32 %s
// MIPS64R2-O32: error: ABI 'o32' is not supported on CPU 'mips64r2'
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
//
// RUN: %clang -target mips64-linux-gnu -### -c %s 2>&1 \
[mips] The default ABI depends on the CPU not the Arch on MTI and IMG vendor triples. Summary: 32-bit CPU's default to O32. 64-bit CPU's default to N64. The default CPU (mips32r2/mips64r2) still depends on the arch so there's no functional change when the CPU isn't specified but commands like: clang -target mips-mti-linux-gnu -mips64r2 will now default to a 64-bit ABI like our gcc toolchains do* instead of asserting in the backend**. Other vendors (including Triple::UnknownVendor) still derive the default ABI from the arch. * Although not the same one as our gcc toolchains, clang has historically defaulted to N64 where gcc defaults to N32. ** Mixing O32 and a 64-bit CPU causing assertions is a long-standing bug. Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21016 llvm-svn: 271884
2016-06-06 20:02:21 +08:00
// RUN: | FileCheck -check-prefix=MIPS64R2-N64 %s
// RUN: %clang -target mips-img-linux-gnu -mips64r2 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R2-N64 %s
// RUN: %clang -target mips-mti-linux-gnu -mips64r2 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R2-N64 %s
[mips] Defer validity check for CPU/ABI pairs and improve error message for invalid cases. Summary: The validity of ABI/CPU pairs is no longer checked on the fly but is instead checked after initialization. As a result, invalid CPU/ABI pairs can be reported as being known but invalid instead of being unknown. For example, we now emit: error: ABI 'n32' is not supported on CPU 'mips32r2' instead of: error: unknown target ABI 'n64' Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21023 llvm-svn: 272645
2016-06-14 16:58:50 +08:00
// RUN: %clang -target mips-linux-gnu -mips64r2 -mabi=64 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R2-N64 %s
[mips] The default ABI depends on the CPU not the Arch on MTI and IMG vendor triples. Summary: 32-bit CPU's default to O32. 64-bit CPU's default to N64. The default CPU (mips32r2/mips64r2) still depends on the arch so there's no functional change when the CPU isn't specified but commands like: clang -target mips-mti-linux-gnu -mips64r2 will now default to a 64-bit ABI like our gcc toolchains do* instead of asserting in the backend**. Other vendors (including Triple::UnknownVendor) still derive the default ABI from the arch. * Although not the same one as our gcc toolchains, clang has historically defaulted to N64 where gcc defaults to N32. ** Mixing O32 and a 64-bit CPU causing assertions is a long-standing bug. Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21016 llvm-svn: 271884
2016-06-06 20:02:21 +08:00
// MIPS64R2-N64: "-target-cpu" "mips64r2"
// MIPS64R2-N64: "-target-abi" "n64"
//
// RUN: %clang -target mips64-linux-gnu -### -mips64r3 -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R3-N64 %s
// RUN: %clang -target mips-img-linux-gnu -mips64r3 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R3-N64 %s
// RUN: %clang -target mips-mti-linux-gnu -mips64r3 -### -c %s 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS64R3-N64 %s
// MIPS64R3-N64: "-target-cpu" "mips64r3"
// MIPS64R3-N64: "-target-abi" "n64"
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
//
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -mabi=32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-32 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-32: "-target-cpu" "mips32r2"
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// MIPS-ABI-32: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -mabi=o32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-O32 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-O32: "-target-cpu" "mips32r2"
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// MIPS-ABI-O32: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -mabi=n32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-N32 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-N32: "-target-cpu" "mips64r2"
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// MIPS-ABI-N32: "-target-abi" "n32"
//
// RUN: %clang -target mips64-linux-gnu -### -c %s \
// RUN: -mabi=64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-64 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-64: "-target-cpu" "mips64r2"
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// MIPS-ABI-64: "-target-abi" "n64"
//
// RUN: %clang -target mips64-linux-gnu -### -c %s \
// RUN: -mabi=n64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-N64 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-N64: "-target-cpu" "mips64r2"
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// MIPS-ABI-N64: "-target-abi" "n64"
//
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// RUN: not %clang -target mips64-linux-gnu -c %s \
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
// RUN: -mabi=o64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-O64 %s
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// MIPS-ABI-O64: error: unknown target ABI 'o64'
[Mips] Convert a GNU style Mips ABI name to the name accepted by LLVM Mips backend. llvm-svn: 179981
2013-04-21 21:30:10 +08:00
//
[Driver][Mips] Check rejecting of invalid MIPS ABI names in the test. No functional changes. llvm-svn: 212022
2014-06-30 16:09:54 +08:00
// RUN: not %clang -target mips-linux-gnu -c %s \
// RUN: -mabi=unknown 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ABI-UNKNOWN %s
// MIPS-ABI-UNKNOWN: error: unknown target ABI 'unknown'
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
[Driver][Mips] Support more MIPS CPU names: mips1 - mips5. llvm-svn: 212338
2014-07-04 20:36:56 +08:00
// RUN: -march=mips1 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-1 %s
// MIPS-ARCH-1: "-target-cpu" "mips1"
// MIPS-ARCH-1: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -march=mips2 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-2 %s
// MIPS-ARCH-2: "-target-cpu" "mips2"
// MIPS-ARCH-2: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -march=mips3 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-3 %s
// MIPS-ARCH-3: "-target-cpu" "mips3"
// MIPS-ARCH-3: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -march=mips4 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-4 %s
// MIPS-ARCH-4: "-target-cpu" "mips4"
// MIPS-ARCH-4: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -march=mips5 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-5 %s
// MIPS-ARCH-5: "-target-cpu" "mips5"
// MIPS-ARCH-5: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
// RUN: -march=mips32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-32 %s
// MIPS-ARCH-32: "-target-cpu" "mips32"
// MIPS-ARCH-32: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
// RUN: -march=mips32r2 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-32R2 %s
// MIPS-ARCH-32R2: "-target-cpu" "mips32r2"
// MIPS-ARCH-32R2: "-target-abi" "o32"
//
// RUN: %clang -target mips-linux-gnu -### -c %s \
[mips][p5600] Add -mcpu=p5600 option. Summary: Reviewers: vkalintiris, atanasyan Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D12234 llvm-svn: 249306
2015-10-05 20:24:30 +08:00
// RUN: -march=p5600 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-P5600 %s
// MIPS-ARCH-P5600: "-target-cpu" "p5600"
// MIPS-ARCH-P5600: "-target-abi" "o32"
//
[mips] The P5600 does not support N32/N64 since it's a 32-bit CPU. Summary: Reviewers: atanasyan Subscribers: cfe-commits, sdardis Differential Revision: http://reviews.llvm.org/D20963 llvm-svn: 271877
2016-06-06 17:47:32 +08:00
// RUN: not %clang -target mips-linux-gnu -c %s \
// RUN: -march=p5600 -mabi=64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-P5600-N64 %s
[mips] Defer validity check for CPU/ABI pairs and improve error message for invalid cases. Summary: The validity of ABI/CPU pairs is no longer checked on the fly but is instead checked after initialization. As a result, invalid CPU/ABI pairs can be reported as being known but invalid instead of being unknown. For example, we now emit: error: ABI 'n32' is not supported on CPU 'mips32r2' instead of: error: unknown target ABI 'n64' Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21023 llvm-svn: 272645
2016-06-14 16:58:50 +08:00
// MIPS-ARCH-P5600-N64: error: ABI 'n64' is not supported on CPU 'p5600'
[mips] The P5600 does not support N32/N64 since it's a 32-bit CPU. Summary: Reviewers: atanasyan Subscribers: cfe-commits, sdardis Differential Revision: http://reviews.llvm.org/D20963 llvm-svn: 271877
2016-06-06 17:47:32 +08:00
//
[mips][p5600] Add -mcpu=p5600 option. Summary: Reviewers: vkalintiris, atanasyan Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D12234 llvm-svn: 249306
2015-10-05 20:24:30 +08:00
// RUN: %clang -target mips-linux-gnu -### -c %s \
[Driver][Mips] If ABI name is not provided deduce it from the target triple not from the CPU name. This approach is closer to the method used by gcc driver. llvm-svn: 212176
2014-07-02 21:20:36 +08:00
// RUN: -march=mips64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-3264 %s
// MIPS-ARCH-3264: "-target-cpu" "mips64"
// MIPS-ARCH-3264: "-target-abi" "o32"
//
// RUN: %clang -target mips64-linux-gnu -### -c %s \
// RUN: -march=mips64 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-64 %s
// MIPS-ARCH-64: "-target-cpu" "mips64"
// MIPS-ARCH-64: "-target-abi" "n64"
//
// RUN: %clang -target mips64-linux-gnu -### -c %s \
// RUN: -march=mips64r2 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-64R2 %s
// MIPS-ARCH-64R2: "-target-cpu" "mips64r2"
// MIPS-ARCH-64R2: "-target-abi" "n64"
[Driver][Mips] Check MIPS CPU name provided to the Clang driver. llvm-svn: 212260
2014-07-03 16:31:23 +08:00
//
[Driver][Mips] Support one more MIPS CPU name - octeon. llvm-svn: 212339
2014-07-04 20:37:04 +08:00
// RUN: %clang -target mips64-linux-gnu -### -c %s \
// RUN: -march=octeon 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-OCTEON %s
// MIPS-ARCH-OCTEON: "-target-cpu" "octeon"
// MIPS-ARCH-OCTEON: "-target-abi" "n64"
//
[Driver][Mips] Check MIPS CPU name provided to the Clang driver. llvm-svn: 212260
2014-07-03 16:31:23 +08:00
// RUN: not %clang -target mips64-linux-gnu -c %s \
// RUN: -march=mips32 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-6432 %s
[mips] Defer validity check for CPU/ABI pairs and improve error message for invalid cases. Summary: The validity of ABI/CPU pairs is no longer checked on the fly but is instead checked after initialization. As a result, invalid CPU/ABI pairs can be reported as being known but invalid instead of being unknown. For example, we now emit: error: ABI 'n32' is not supported on CPU 'mips32r2' instead of: error: unknown target ABI 'n64' Reviewers: atanasyan Subscribers: sdardis, cfe-commits Differential Revision: http://reviews.llvm.org/D21023 llvm-svn: 272645
2016-06-14 16:58:50 +08:00
// MIPS-ARCH-6432: error: ABI 'n64' is not supported on CPU 'mips32'
[Driver][Mips] Check MIPS CPU name provided to the Clang driver. llvm-svn: 212260
2014-07-03 16:31:23 +08:00
//
// RUN: not %clang -target mips-linux-gnu -c %s \
// RUN: -march=unknown 2>&1 \
// RUN: | FileCheck -check-prefix=MIPS-ARCH-UNKNOWN %s
// MIPS-ARCH-UNKNOWN: error: unknown target CPU 'unknown'
[driver][mips] Adjust target triple accordingly to provided ABI name Explicitly selected MIPS ABI using the `-mabi` option implies corresponding target triple. For 'O32' ABI it's a 32-bit target triple like `mips-linux-gnu`. For 'N32' and 'N64' ABIs it's a 64-bit target triple like `mips64-linux-gnu`. This patch adjusts target triple accordingly these rules like we do for pseudo-target flags '-m64', '-m32' etc already. Differential revision: https://reviews.llvm.org/D52290 llvm-svn: 343169
2018-09-27 13:04:50 +08:00
// Check adjusting of target triple accordingly to `-mabi` option.
// RUN: %clang -target mips64-linux-gnu -mabi=32 -### %s 2>&1 \
// RUN: | FileCheck -check-prefix=TARGET-O32 %s
// TARGET-O32: "-triple" "mips-unknown-linux-gnu"
// TARGET-O32: "-target-cpu" "mips32r2"
// TARGET-O32: "-target-abi" "o32"
Fix greedy FileCheck expression in test/Driver/mips-abi.c 'ld{{.*}}"' seems to match the complete line for me which is failing the test. Only allow an optional '.exe' for Windows systems as most other tests do. Another possibility would be to collapse the greedy expression with the next check to avoid matching the full line. Differential Revision: https://reviews.llvm.org/D52619 llvm-svn: 343240
2018-09-28 01:27:48 +08:00
// TARGET-O32: ld{{(.exe)?}}"
[driver][mips] Adjust target triple accordingly to provided ABI name Explicitly selected MIPS ABI using the `-mabi` option implies corresponding target triple. For 'O32' ABI it's a 32-bit target triple like `mips-linux-gnu`. For 'N32' and 'N64' ABIs it's a 64-bit target triple like `mips64-linux-gnu`. This patch adjusts target triple accordingly these rules like we do for pseudo-target flags '-m64', '-m32' etc already. Differential revision: https://reviews.llvm.org/D52290 llvm-svn: 343169
2018-09-27 13:04:50 +08:00
// TARGET-O32: "-m" "elf32btsmip"
// RUN: %clang -target mips-linux-gnu -mabi=n32 -### %s 2>&1 \
// RUN: | FileCheck -check-prefix=TARGET-N32 %s
// TARGET-N32: "-triple" "mips64-unknown-linux-gnu"
// TARGET-N32: "-target-cpu" "mips64r2"
// TARGET-N32: "-target-abi" "n32"
Fix greedy FileCheck expression in test/Driver/mips-abi.c 'ld{{.*}}"' seems to match the complete line for me which is failing the test. Only allow an optional '.exe' for Windows systems as most other tests do. Another possibility would be to collapse the greedy expression with the next check to avoid matching the full line. Differential Revision: https://reviews.llvm.org/D52619 llvm-svn: 343240
2018-09-28 01:27:48 +08:00
// TARGET-N32: ld{{(.exe)?}}"
[driver][mips] Adjust target triple accordingly to provided ABI name Explicitly selected MIPS ABI using the `-mabi` option implies corresponding target triple. For 'O32' ABI it's a 32-bit target triple like `mips-linux-gnu`. For 'N32' and 'N64' ABIs it's a 64-bit target triple like `mips64-linux-gnu`. This patch adjusts target triple accordingly these rules like we do for pseudo-target flags '-m64', '-m32' etc already. Differential revision: https://reviews.llvm.org/D52290 llvm-svn: 343169
2018-09-27 13:04:50 +08:00
// TARGET-N32: "-m" "elf32btsmipn32"
// RUN: %clang -target mips-linux-gnu -mabi=64 -### %s 2>&1 \
// RUN: | FileCheck -check-prefix=TARGET-N64 %s
// TARGET-N64: "-triple" "mips64-unknown-linux-gnu"
// TARGET-N64: "-target-cpu" "mips64r2"
// TARGET-N64: "-target-abi" "n64"
Fix greedy FileCheck expression in test/Driver/mips-abi.c 'ld{{.*}}"' seems to match the complete line for me which is failing the test. Only allow an optional '.exe' for Windows systems as most other tests do. Another possibility would be to collapse the greedy expression with the next check to avoid matching the full line. Differential Revision: https://reviews.llvm.org/D52619 llvm-svn: 343240
2018-09-28 01:27:48 +08:00
// TARGET-N64: ld{{(.exe)?}}"
[driver][mips] Adjust target triple accordingly to provided ABI name Explicitly selected MIPS ABI using the `-mabi` option implies corresponding target triple. For 'O32' ABI it's a 32-bit target triple like `mips-linux-gnu`. For 'N32' and 'N64' ABIs it's a 64-bit target triple like `mips64-linux-gnu`. This patch adjusts target triple accordingly these rules like we do for pseudo-target flags '-m64', '-m32' etc already. Differential revision: https://reviews.llvm.org/D52290 llvm-svn: 343169
2018-09-27 13:04:50 +08:00
// TARGET-N64: "-m" "elf64btsmip"