[cfe-commits] r65973 - in /cfe/trunk: lib/Sema/SemaDeclObjC.cpp test/SemaObjC/property-nonfragile-abi.m

[Fariborz Jahanian]

On Mar 3, 2009, at 2:48 PM, Fariborz Jahanian wrote:

>
> On Mar 3, 2009, at 2:45 PM, steve naroff wrote:
>
>>
>> On Mar 3, 2009, at 5:27 PM, Fariborz Jahanian wrote:
>>
>>>
>>> On Mar 3, 2009, at 2:17 PM, Fariborz Jahanian wrote:
>>>
>>>> We can't really turn off this error message for non-fragile abi
>>>> until
>>>> we implement synthesizing the ivar in non-fragile abi.
>>>> Test case probably blows up with -S
>>>
>>> And of course it does not blow up, because we told the back-end to
>>> skip code gen if ivar is missing :).
>>>
>>
>> Thanks for the update.
>>
>> Seems like my (front-end) change is o.k...true?
>
> OK. I will shortly change ir gen to issue unimplemented feature.
> Other clients should do likewise, if they do nonfragile-abi stuff.

After further looking into this, it is not a good idea to remove the  
error for non-fragile abi at all.
Try this test case with -arch x86_64 with -fsyntax-only:

@interface FOO
@property (assign)int P;
@end
@implementation FOO
   @synthesize P;
   - (int) Meth {return P; }
@end

Problem is that the ivar may be used any where after @synthesize  
directive. Besides, we issue no error and
yet we do not generate the AST for the property.

- Fariborz



>
>
> - fariborz
>
>>
>>
>> Thanks,
>>
>> snaroff
>>
>>> - fj
>>>
>>>>
>>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits