llvm-6502/test/FrontendObjC/2008-11-25-Blocks.m

// RUN: %llvmgcc -S %s -o /dev/null
// rdar://6394879

@interface bork
- (id)B:(void (^)())blk;
- (void)C;
@end
@implementation bork
- (id)B:(void (^)())blk {
  __attribute__((__blocks__(byref))) bork* new = ((void *)0);
  blk();
}
- (void)C {
  __attribute__((__blocks__(byref))) id var;
  [self B:^() {}];
}
@end
Remove explicit uses of -emit-llvm, the test infrastructure adds it automatically. Use -S with llvm-gcc rather than -c, so tests can work when llvm-gcc is really dragonegg (which can output IR with -S but not -c). Yes, dragonegg supports objective-c (poorly though). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@120163 91177308-0d34-0410-b5e6-96231b3b80d8 2010-11-25 21:46:07 +00:00			`// RUN: %llvmgcc -S %s -o /dev/null`
Add test for rdar://6394879. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60079 91177308-0d34-0410-b5e6-96231b3b80d8 2008-11-26 02:21:12 +00:00			`// rdar://6394879`

			`@interface bork`
			`- (id)B:(void (^)())blk;`
			`- (void)C;`
			`@end`
			`@implementation bork`
			`- (id)B:(void (^)())blk {`
			`__attribute__((__blocks__(byref))) bork* new = ((void *)0);`
			`blk();`
			`}`
			`- (void)C {`
			`__attribute__((__blocks__(byref))) id var;`
			`[self B:^() {}];`
			`}`
			`@end`