File: nil-receiver.mm

package info (click to toggle)
llvm-toolchain-9 1%3A9.0.1-16.1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 882,388 kB
  • sloc: cpp: 4,167,636; ansic: 714,256; asm: 457,610; python: 155,927; objc: 65,094; sh: 42,856; lisp: 26,908; perl: 7,786; pascal: 7,722; makefile: 6,881; ml: 5,581; awk: 3,648; cs: 2,027; xml: 888; javascript: 381; ruby: 156
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}}
}