maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGenObjC/fpret.m

39 lines
1.4 KiB
Mathematica
Raw Normal View History

Restructure how the driver communicates information about the target Objective-C runtime down to the frontend: break this down into a single target runtime kind and version, and compute all the relevant information from that. This makes it relatively painless to add support for new runtimes to the compiler. Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z, available at the driver level as a better and more general alternative to -fgnu-runtime and -fnext-runtime. This new concept of an Objective-C runtime also encompasses what we were previously separating out as the "Objective-C ABI", so fragile vs. non-fragile runtimes are now really modelled as different kinds of runtime, paving the way for better overall differentiation. As a sort of special case, continue to accept the -cc1 flag -fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak. I won't go so far as to say "no functionality change", even ignoring the new driver flag, but subtle changes in driver semantics are almost certainly not intended. llvm-svn: 158793
2012-06-20 14:18:46 +08:00
// RUN: %clang_cc1 -triple i386-apple-darwin9 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -o - %s | \
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// RUN: FileCheck --check-prefix=CHECK-X86_32 %s
//
Restructure how the driver communicates information about the target Objective-C runtime down to the frontend: break this down into a single target runtime kind and version, and compute all the relevant information from that. This makes it relatively painless to add support for new runtimes to the compiler. Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z, available at the driver level as a better and more general alternative to -fgnu-runtime and -fnext-runtime. This new concept of an Objective-C runtime also encompasses what we were previously separating out as the "Objective-C ABI", so fragile vs. non-fragile runtimes are now really modelled as different kinds of runtime, paving the way for better overall differentiation. As a sort of special case, continue to accept the -cc1 flag -fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak. I won't go so far as to say "no functionality change", even ignoring the new driver flag, but subtle changes in driver semantics are almost certainly not intended. llvm-svn: 158793
2012-06-20 14:18:46 +08:00
// RUN: %clang_cc1 -triple x86_64-apple-darwin10 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -o - %s | \
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// RUN: FileCheck --check-prefix=CHECK-X86_64 %s
//
Restructure how the driver communicates information about the target Objective-C runtime down to the frontend: break this down into a single target runtime kind and version, and compute all the relevant information from that. This makes it relatively painless to add support for new runtimes to the compiler. Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z, available at the driver level as a better and more general alternative to -fgnu-runtime and -fnext-runtime. This new concept of an Objective-C runtime also encompasses what we were previously separating out as the "Objective-C ABI", so fragile vs. non-fragile runtimes are now really modelled as different kinds of runtime, paving the way for better overall differentiation. As a sort of special case, continue to accept the -cc1 flag -fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak. I won't go so far as to say "no functionality change", even ignoring the new driver flag, but subtle changes in driver semantics are almost certainly not intended. llvm-svn: 158793
2012-06-20 14:18:46 +08:00
// RUN: %clang_cc1 -triple armv7-apple-darwin10 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -target-abi apcs-gnu -o - %s | \
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// RUN: FileCheck --check-prefix=CHECK-ARMV7 %s
@interface A
-(float) floatValue;
-(double) doubleValue;
-(long double) longDoubleValue;
@end
// CHECK-X86_32: define void @t0()
Revert r126678. llvm-svn: 126685
2011-03-01 05:19:34 +08:00
// CHECK-X86_32: call float bitcast {{.*}} @objc_msgSend_fpret to
objc IRGen for Next runtime message API. The prototype for objc_msgSend() is technically variadic - `id objc_msgSend(id, SEL, ...)`. But all method calls should use a prototype that matches the method, not the prototype for objc_msgSend itself(). // rdar://9048030 llvm-svn: 126754
2011-03-02 01:28:13 +08:00
// CHECK-X86_32: call double bitcast {{.*}} @objc_msgSend_fpret to
Revert r126678. llvm-svn: 126685
2011-03-01 05:19:34 +08:00
// CHECK-X86_32: call x86_fp80 bitcast {{.*}} @objc_msgSend_fpret to
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// CHECK-X86_32: }
//
// CHECK-X86_64: define void @t0()
Revert r126678. llvm-svn: 126685
2011-03-01 05:19:34 +08:00
// CHECK-X86_64: call float bitcast {{.*}} @objc_msgSend to
// CHECK-X86_64: call double bitcast {{.*}} @objc_msgSend to
// CHECK-X86_64: call x86_fp80 bitcast {{.*}} @objc_msgSend_fpret to
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// CHECK-X86_64: }
//
// CHECK-ARMV7: define void @t0()
Revert r126678. llvm-svn: 126685
2011-03-01 05:19:34 +08:00
// CHECK-ARMV7: call float bitcast {{.*}} @objc_msgSend to
// CHECK-ARMV7: call double bitcast {{.*}} @objc_msgSend to
// CHECK-ARMV7: call double bitcast {{.*}} @objc_msgSend to
IRgen: Add a test case I forgot to commit at some point. llvm-svn: 108713
2010-07-20 01:11:38 +08:00
// CHECK-ARMV7: }
void t0() {
[(A*)0 floatValue];
[(A*)0 doubleValue];
[(A*)0 longDoubleValue];
}