File: nil-receiver.mm

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-16
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,496,368 kB
  • sloc: cpp: 5,593,980; ansic: 986,873; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,547; xml: 953; cs: 573; fortran: 567
file content (24 lines) | stat: -rw-r--r-- 556 bytes parent folder | download | duplicates (23) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
// RUN: %clang_analyze_cc1 -analyzer-checker=core,debug.ExprInspection \
// RUN:                    -verify %s

#define nil ((id)0)

void clang_analyzer_eval(int);

struct S {
  int x;
  S();
};

@interface I
@property S s;
@end

void foo() {
  // This produces a zero-initialized structure.
  // FIXME: This very fact does deserve the warning, because zero-initialized
  // structures aren't always valid in C++. It's particularly bad when the
  // object has a vtable.
  S s = ((I *)nil).s;
  clang_analyzer_eval(s.x == 0); // expected-warning{{TRUE}}
}