forked from OSchip/llvm-project
[analyzer] Dump the environment entry kind as well
By this change the `exploded-graph-rewriter` will display the class kind of the expression of the environment entry. It makes easier to decide if the given entry corresponds to the lvalue or to the rvalue of some expression. It turns out the rewriter already had support for visualizing it, but probably was never actually used? Reviewed By: martong Differential Revision: https://reviews.llvm.org/D132109
This commit is contained in:
parent
955e6ac499
commit
7cddf9cad1
|
@ -274,7 +274,8 @@ void Environment::printJson(raw_ostream &Out, const ASTContext &Ctx,
|
|||
|
||||
const Stmt *S = I->first.getStmt();
|
||||
Indent(Out, InnerSpace, IsDot)
|
||||
<< "{ \"stmt_id\": " << S->getID(Ctx) << ", \"pretty\": ";
|
||||
<< "{ \"stmt_id\": " << S->getID(Ctx) << ", \"kind\": \""
|
||||
<< S->getStmtClassName() << "\", \"pretty\": ";
|
||||
S->printJson(Out, nullptr, PP, /*AddQuotes=*/true);
|
||||
|
||||
Out << ", \"value\": ";
|
||||
|
|
|
@ -36,7 +36,7 @@ void foo(int x) {
|
|||
// CHECK-NEXT: ]},
|
||||
// CHECK-NEXT: "environment": { "pointer": "{{0x[0-9a-f]+}}", "items": [
|
||||
// CHECK-NEXT: { "lctx_id": {{[0-9]+}}, "location_context": "#0 Call", "calling": "foo", "location": null, "items": [
|
||||
// CHECK-NEXT: { "stmt_id": {{[0-9]+}}, "pretty": "clang_analyzer_printState", "value": "&code{clang_analyzer_printState}" }
|
||||
// CHECK-NEXT: { "stmt_id": {{[0-9]+}}, "kind": "ImplicitCastExpr", "pretty": "clang_analyzer_printState", "value": "&code{clang_analyzer_printState}" }
|
||||
// CHECK-NEXT: ]}
|
||||
// CHECK-NEXT: ]},
|
||||
// CHECK-NEXT: "constraints": [
|
||||
|
|
Loading…
Reference in New Issue