Displaying 1 result from an estimated 1 matches for "__blocks__".
2008 Nov 25
2
[LLVMdev] RFA: tree-nested.c
...default:
...
}
What are the assumptions going into this "walk_all_functions" call?
Should the code have been placed into some nesting info slot or
something?
FYI, here's the code in question:
$ cat testcase.i
typedef struct A *ARef;
@implementation bork
- (id)B {
__attribute__((__blocks__(byref))) bork* new = ((void *)0);
}
- (void)C {
__attribute__((__blocks__(byref))) id var;
[self func:^() {}];
}
@end
$ llvm-gcc -x objective-c -std=gnu99 -c testcase.i
testcase.i:9: internal compiler error: in lookup_context_for_decl, at
tree-nested.c:1680
Please submit a full bug report,
wit...