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/arm-long-calls.c

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

16 lines
533 B
C
Raw Normal View History

Driver: add -m{,no-}long-calls support This mirrors the GCC option for the ARM backend. This option enables the backend option "-enable-arm-long-calls". The default behaviour is that this is disabled due to the slight overhead of the generated calls. If the target of jumps are greater than 64M range of offset-based jumps, then the target address must be loaded into a register to make an indirect jump. The backend support for this has been present, but was not previously controllable by the proper flag. llvm-svn: 210398
2014-06-08 03:32:38 +08:00
// RUN: %clang -target armv7-eabi -### %s 2>&1 \
// RUN: | FileCheck %s -check-prefix CHECK-DEFAULT
// RUN: %clang -target armv7-eabi -### -mlong-calls %s 2>&1 \
// RUN: | FileCheck %s -check-prefix CHECK-LONG-CALLS
// RUN: %clang -target armv7-eabi -### -mlong-calls -mno-long-calls %s 2>&1 \
// RUN: | FileCheck %s -check-prefix CHECK-NO-LONG-CALLS
[ARM] Pass subtarget feature "+long-calls" instead of passing backend option "-arm-long-calls". This change allows using -mlong-calls/-mno-long-calls for LTO and enabling or disabling long call on a per-function basis. rdar://problem/21529937 Differential Revision: http://reviews.llvm.org/D9414 llvm-svn: 241565
2015-07-07 14:42:05 +08:00
// CHECK-DEFAULT-NOT: "-target-feature" "+long-calls"
Driver: add -m{,no-}long-calls support This mirrors the GCC option for the ARM backend. This option enables the backend option "-enable-arm-long-calls". The default behaviour is that this is disabled due to the slight overhead of the generated calls. If the target of jumps are greater than 64M range of offset-based jumps, then the target address must be loaded into a register to make an indirect jump. The backend support for this has been present, but was not previously controllable by the proper flag. llvm-svn: 210398
2014-06-08 03:32:38 +08:00
[ARM] Pass subtarget feature "+long-calls" instead of passing backend option "-arm-long-calls". This change allows using -mlong-calls/-mno-long-calls for LTO and enabling or disabling long call on a per-function basis. rdar://problem/21529937 Differential Revision: http://reviews.llvm.org/D9414 llvm-svn: 241565
2015-07-07 14:42:05 +08:00
// CHECK-LONG-CALLS: "-target-feature" "+long-calls"
Driver: add -m{,no-}long-calls support This mirrors the GCC option for the ARM backend. This option enables the backend option "-enable-arm-long-calls". The default behaviour is that this is disabled due to the slight overhead of the generated calls. If the target of jumps are greater than 64M range of offset-based jumps, then the target address must be loaded into a register to make an indirect jump. The backend support for this has been present, but was not previously controllable by the proper flag. llvm-svn: 210398
2014-06-08 03:32:38 +08:00
[ARM] Pass subtarget feature "+long-calls" instead of passing backend option "-arm-long-calls". This change allows using -mlong-calls/-mno-long-calls for LTO and enabling or disabling long call on a per-function basis. rdar://problem/21529937 Differential Revision: http://reviews.llvm.org/D9414 llvm-svn: 241565
2015-07-07 14:42:05 +08:00
// CHECK-NO-LONG-CALLS-NOT: "-target-feature" "+long-calls"
Driver: add -m{,no-}long-calls support This mirrors the GCC option for the ARM backend. This option enables the backend option "-enable-arm-long-calls". The default behaviour is that this is disabled due to the slight overhead of the generated calls. If the target of jumps are greater than 64M range of offset-based jumps, then the target address must be loaded into a register to make an indirect jump. The backend support for this has been present, but was not previously controllable by the proper flag. llvm-svn: 210398
2014-06-08 03:32:38 +08:00