6a76a1639f
Both -analyze-function and -analyzer-display-progress now share the same convention for naming functions, which allows discriminating between methods with the same name in different classes, C++ overloads, and also presents Objective-C instance and class methods in the convenient notation. This also allows looking up the name for the particular function you're trying to restrict analysis to in the -analyzer-display-progress output, in case it was not instantly obvious. Differential Revision: https://reviews.llvm.org/D22856 llvm-svn: 278018
31 lines
748 B
Objective-C
31 lines
748 B
Objective-C
// RUN: %clang_cc1 -fblocks -analyze -analyzer-display-progress %s 2>&1 | FileCheck %s
|
|
|
|
#include "Inputs/system-header-simulator-objc.h"
|
|
|
|
static void f() {}
|
|
|
|
@interface I: NSObject
|
|
-(void)instanceMethod:(int)arg1 with:(int)arg2;
|
|
+(void)classMethod;
|
|
@end
|
|
|
|
@implementation I
|
|
-(void)instanceMethod:(int)arg1 with:(int)arg2 {}
|
|
+(void)classMethod {}
|
|
@end
|
|
|
|
void g(I *i, int x, int y) {
|
|
[I classMethod];
|
|
[i instanceMethod: x with: y];
|
|
|
|
void (^block)(void);
|
|
block = ^{};
|
|
block();
|
|
}
|
|
|
|
// CHECK: analyzer-display-progress.m f
|
|
// CHECK: analyzer-display-progress.m -[I instanceMethod:with:]
|
|
// CHECK: analyzer-display-progress.m +[I classMethod]
|
|
// CHECK: analyzer-display-progress.m g
|
|
// CHECK: analyzer-display-progress.m block (line: 22, col: 11)
|