File: nil-receiver.mm

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (24 lines) | stat: -rw-r--r-- 556 bytes parent folder | download | duplicates (25) 
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}}
}