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/darwin-embedded.c

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

62 lines
2.4 KiB
C
Raw Normal View History

Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// RUN: %clang -target x86_64-apple-darwin -arch armv6m -resource-dir=%S/Inputs/resource_dir %s -### 2> %t
// RUN: %clang -target x86_64-apple-darwin -arch armv7em -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
ARM: make Darwin's "-arch armv7em" default to hard-float. We've already paid the price for separate "armv7m" and "armv7em" slices (support in other tools), it's silly to make them identical other than the default CPU. rdar://23055688 llvm-svn: 266211
2016-04-14 01:08:51 +08:00
// RUN: %clang -target x86_64-apple-darwin -arch armv7em -mfloat-abi=soft -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// RUN: %clang -target x86_64-apple-darwin -arch armv7m -fPIC -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
ARM MachO embedded: fix test without FileCheck line Well, that's one way to pass a test, I suppose. Unfortunately actually doing the testing means I didn't pass all I thought (embedded v7a is not supported, apparently). I'll deal with that with the move to -none-macho rather than putting heinous hacks in right now. llvm-svn: 197240
2013-12-14 00:05:12 +08:00
// RUN: %clang -target x86_64-apple-darwin -arch armv7em -fPIC -mfloat-abi=hard -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
// RUN: %clang -target x86_64-apple-darwin -arch armv7em -fPIC -mfloat-abi=softfp -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
MachO: use *-*-*-macho for MachO embedded targets. Previously we had bodged together some hacks mapping MachO embedded targets (i.e. mainly ARM v6M and v7M) to the "*-*-darwin-eabi" triple. This is incorrect in both details (they don't run Darwin and they're not EABI in any real sense). This commit appropriates the existing "MachO" environment for the purpose instead. llvm-svn: 199367
2014-01-16 16:48:16 +08:00
// RUN: %clang -target x86_64-apple-none-macho -arch armv7 -mhard-float -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
// RUN: %clang -target x86_64-apple-none-macho -arch armv7 -msoft-float -fPIC -resource-dir=%S/Inputs/resource_dir %s -### 2>> %t
ARM MachO embedded: fix test without FileCheck line Well, that's one way to pass a test, I suppose. Unfortunately actually doing the testing means I didn't pass all I thought (embedded v7a is not supported, apparently). I'll deal with that with the move to -none-macho rather than putting heinous hacks in right now. llvm-svn: 197240
2013-12-14 00:05:12 +08:00
// RUN: FileCheck %s < %t
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// ARMv6m has no float
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "soft"
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// CHECK: libclang_rt.soft_static.a
ARM: make Darwin's "-arch armv7em" default to hard-float. We've already paid the price for separate "armv7m" and "armv7em" slices (support in other tools), it's silly to make them identical other than the default CPU. rdar://23055688 llvm-svn: 266211
2016-04-14 01:08:51 +08:00
// ARMv7em does
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
ARM: make Darwin's "-arch armv7em" default to hard-float. We've already paid the price for separate "armv7m" and "armv7em" slices (support in other tools), it's silly to make them identical other than the default CPU. rdar://23055688 llvm-svn: 266211
2016-04-14 01:08:51 +08:00
// CHECK: "-mfloat-abi" "hard"
// CHECK: libclang_rt.hard_static.a
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
ARM: make Darwin's "-arch armv7em" default to hard-float. We've already paid the price for separate "armv7m" and "armv7em" slices (support in other tools), it's silly to make them identical other than the default CPU. rdar://23055688 llvm-svn: 266211
2016-04-14 01:08:51 +08:00
// but the ABI can be overridden
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
ARM: make Darwin's "-arch armv7em" default to hard-float. We've already paid the price for separate "armv7m" and "armv7em" slices (support in other tools), it's silly to make them identical other than the default CPU. rdar://23055688 llvm-svn: 266211
2016-04-14 01:08:51 +08:00
// CHECK: "-target-feature" "+soft-float"
// CHECK: "-mfloat-abi" "soft"
// CHECK: libclang_rt.soft_static.a
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// ARMv7m has no float either
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "soft"
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// CHECK: libclang_rt.soft_pic.a
ARM MachO embedded: fix test without FileCheck line Well, that's one way to pass a test, I suppose. Unfortunately actually doing the testing means I didn't pass all I thought (embedded v7a is not supported, apparently). I'll deal with that with the move to -none-macho rather than putting heinous hacks in right now. llvm-svn: 197240
2013-12-14 00:05:12 +08:00
// But it can be enabled on ARMv7em
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "hard"
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// CHECK: libclang_rt.hard_pic.a
// "softfp" must link against a soft-float library since that's what the
// callers we're compiling will expect.
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "soft"
Darwin-embedded: find correct libclang_rt for embedded targets. This refactors some of the Darwin toolchain classification to give a more solid distinction between the three primary Darwin platforms (OS X, IOS and IOS simulator) so that a 4th choice can be added temporarily: embedded MachO targets. Longer term, this support will be factored out into a separate class and no longer classified as "darwin-eabi", but the refactoring should still be useful. llvm-svn: 197148
2013-12-12 19:55:52 +08:00
// CHECK: libclang_rt.soft_pic.a
ARM MachO embedded: fix test without FileCheck line Well, that's one way to pass a test, I suppose. Unfortunately actually doing the testing means I didn't pass all I thought (embedded v7a is not supported, apparently). I'll deal with that with the move to -none-macho rather than putting heinous hacks in right now. llvm-svn: 197240
2013-12-14 00:05:12 +08:00
MachO: use *-*-*-macho for MachO embedded targets. Previously we had bodged together some hacks mapping MachO embedded targets (i.e. mainly ARM v6M and v7M) to the "*-*-darwin-eabi" triple. This is incorrect in both details (they don't run Darwin and they're not EABI in any real sense). This commit appropriates the existing "MachO" environment for the purpose instead. llvm-svn: 199367
2014-01-16 16:48:16 +08:00
// -arch "armv7" (== embedded v7a) can be used in a couple of variants:
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "hard"
MachO: use *-*-*-macho for MachO embedded targets. Previously we had bodged together some hacks mapping MachO embedded targets (i.e. mainly ARM v6M and v7M) to the "*-*-darwin-eabi" triple. This is incorrect in both details (they don't run Darwin and they're not EABI in any real sense). This commit appropriates the existing "MachO" environment for the purpose instead. llvm-svn: 199367
2014-01-16 16:48:16 +08:00
// CHECK: libclang_rt.hard_static.a
MachO embedded: default to soft float without issuing warning This is a simpler rule, broadly in line with previous Darwin (which chose between "soft" and "softfp") but probably safer. In practice the only real reason for "softfp" is ABI compatibility, not usually an issue on limited chips like these, so anyone who wanted hard-float should already be saying so. That's my story and I'm sticking to it. rdar://problem/15887493 llvm-svn: 199896
2014-01-23 23:00:01 +08:00
// CHECK-LABEL: Target:
// CHECK-NOT: warning: unknown platform
// CHECK: "-mfloat-abi" "soft"
MachO: use *-*-*-macho for MachO embedded targets. Previously we had bodged together some hacks mapping MachO embedded targets (i.e. mainly ARM v6M and v7M) to the "*-*-darwin-eabi" triple. This is incorrect in both details (they don't run Darwin and they're not EABI in any real sense). This commit appropriates the existing "MachO" environment for the purpose instead. llvm-svn: 199367
2014-01-16 16:48:16 +08:00
// CHECK: libclang_rt.soft_pic.a