Is this even meaningful? Should we at least warn on a void property?

On Jan 13, 2014, at 2:23 , Scott Talbot <[email protected]> wrote:

> Since LLVM r187963, clang has crashed when producing DWARF debug info for an 
> ObjC property of type void.
> This testcase simply checks that that doesn't happen, I have a fix for LLVM 
> separate to this.
> 
> -Scott
> 
> ---
> test/CodeGenObjC/property-type-void.m | 8 ++++++++
> 1 file changed, 8 insertions(+)
> create mode 100644 test/CodeGenObjC/property-type-void.m
> 
diff --git a/test/CodeGenObjC/property-type-void.m b/test/CodeGenObjC/property-type-void.m
new file mode 100644
index 0000000..f57b68c
--- /dev/null
+++ b/test/CodeGenObjC/property-type-void.m
@@ -0,0 +1,8 @@
+// RUN: %clang_cc1 -S -gdwarf-2 -Wno-objc-root-class -x objective-c < %s > /dev/null 2>&1
+
+@interface Foo
+@property (nonatomic,assign,readonly) void foo;
+@end
+@implementation Foo
+- (void)foo {}
+@end
> _______________________________________________
> cfe-commits mailing list
> [email protected]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to