llvm-project/clang/test/CodeGenObjC/overloadable.m

// rdar://6657613
// RUN: %clang_cc1 -emit-llvm %s -o %t

@class C;

// RUN: grep _Z1fP11objc_object %t | count 1
void __attribute__((overloadable)) f(id c) { }

// RUN: grep _Z1fP1C %t | count 1
void __attribute__((overloadable)) f(C *c) { }
add rdar# llvm-svn: 66356 2009-03-08 09:43:34 +08:00			`// rdar://6657613`
Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446 2009-12-16 04:14:24 +08:00			`// RUN: %clang_cc1 -emit-llvm %s -o %t`
Mangle Objective-C interfaces correctly (where correctly refers to what gcc does) llvm-svn: 66349 2009-03-08 06:03:21 +08:00
			`@class C;`

Eliminate &&s in tests. - 'for i in $(find . -type f); do sed -e 's#\(RUN:.[^ ]\) && *$#\1#g' $i \| FileUpdate $i; done', for the curious. llvm-svn: 86430 2009-11-08 09:45:36 +08:00			`// RUN: grep _Z1fP11objc_object %t \| count 1`
This patch includes a conceptually simple, but very intrusive/pervasive change. The idea is to segregate Objective-C "object" pointers from general C pointers (utilizing the recently added ObjCObjectPointerType). The fun starts in Sema::GetTypeForDeclarator(), where "SomeInterface *" is now represented by a single AST node (rather than a PointerType whose Pointee is an ObjCInterfaceType). Since a significant amount of code assumed ObjC object pointers where based on C pointers/structs, this patch is very tedious. It should also explain why it is hard to accomplish this in smaller, self-contained patches. This patch does most of the "heavy lifting" related to moving from PointerType->ObjCObjectPointerType. It doesn't include all potential "cleanups". The good news is additional cleanups can be done later (some are noted in the code). This patch is so large that I didn't want to include any changes that are purely aesthetic. By making the ObjC types truly built-in, they are much easier to work with (and require fewer "hacks"). For example, there is no need for ASTContext::isObjCIdStructType() or ASTContext::isObjCClassStructType()! We believe this change (and the follow-up cleanups) will pay dividends over time. Given the amount of code change, I do expect some fallout from this change (though it does pass all of the clang tests). If you notice any problems, please let us know asap! Thanks. llvm-svn: 75314 2009-07-11 07:34:53 +08:00			`void __attribute__((overloadable)) f(id c) { }`
Mangle Objective-C interfaces correctly (where correctly refers to what gcc does) llvm-svn: 66349 2009-03-08 06:03:21 +08:00
fix test llvm-svn: 66352 2009-03-08 07:39:35 +08:00			`// RUN: grep _Z1fP1C %t \| count 1`
This patch includes a conceptually simple, but very intrusive/pervasive change. The idea is to segregate Objective-C "object" pointers from general C pointers (utilizing the recently added ObjCObjectPointerType). The fun starts in Sema::GetTypeForDeclarator(), where "SomeInterface *" is now represented by a single AST node (rather than a PointerType whose Pointee is an ObjCInterfaceType). Since a significant amount of code assumed ObjC object pointers where based on C pointers/structs, this patch is very tedious. It should also explain why it is hard to accomplish this in smaller, self-contained patches. This patch does most of the "heavy lifting" related to moving from PointerType->ObjCObjectPointerType. It doesn't include all potential "cleanups". The good news is additional cleanups can be done later (some are noted in the code). This patch is so large that I didn't want to include any changes that are purely aesthetic. By making the ObjC types truly built-in, they are much easier to work with (and require fewer "hacks"). For example, there is no need for ASTContext::isObjCIdStructType() or ASTContext::isObjCClassStructType()! We believe this change (and the follow-up cleanups) will pay dividends over time. Given the amount of code change, I do expect some fallout from this change (though it does pass all of the clang tests). If you notice any problems, please let us know asap! Thanks. llvm-svn: 75314 2009-07-11 07:34:53 +08:00			`void __attribute__((overloadable)) f(C *c) { }`