This is an archive of the discontinued LLVM Phabricator instance.

[-Wcalled-once] Do not run analysis on Obj-C++
ClosedPublic

Authored by vsavchenko on Apr 21 2021, 6:51 AM.

Details

Summary

Objective-C++ is not yet suppoerted.

rdar://76729552

Diff Detail

Event Timeline

vsavchenko created this revision.Apr 21 2021, 6:51 AM
vsavchenko requested review of this revision.Apr 21 2021, 6:51 AM
Herald added a project: Restricted Project. · View Herald TranscriptApr 21 2021, 6:51 AM
Herald added a subscriber: cfe-commits. · View Herald Transcript
NoQ accepted this revision.Apr 21 2021, 9:56 AM

Ok then!

This revision is now accepted and ready to land.Apr 21 2021, 9:56 AM
This revision was automatically updated to reflect the committed changes.
thakis added a subscriber: thakis.Jan 15 2023, 6:11 AM

Can you say a few words on _why_ this is emitted in only Objective-C? What's missing for Objective-C++? I was surprised that this warning fired in a .m file but not in a .mm file.

Herald added a project: Restricted Project. · View Herald TranscriptJan 15 2023, 6:11 AM

Can you say a few words on _why_ this is emitted in only Objective-C? What's missing for Objective-C++? I was surprised that this warning fired in a .m file but not in a .mm file.

Technically there is nothing that prevents us from supporting Objective-C++, but the warning implementation will need to handle it correctly. Currently, it doesn't support lambda expressions and C++ exceptions from the top of my head. Probably there are more language constructs that can cause incorrect warnings. Long story short, it needs additional logic and testing.

Cheers!