mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2025-02-03 07:38:57 +00:00
b591845f4b
the assertion is in fact incorrect: there is a cornercase in Objective-C++ in which a C++ object is not constructed with a constructor, but merely zero-initialized. Namely, this happens when an Objective-C message is sent to a nil and it is supposed to return a C++ object. Differential Revision: https://reviews.llvm.org/D60988 llvm-svn: 359262
25 lines
556 B
Plaintext
25 lines
556 B
Plaintext
// 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}}
|
|
}
|