mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-30 13:46:09 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/clang/test/AST/ast-dump-record-definition-data-json.cpp

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

5346 lines
162 KiB
C++
Raw Normal View History

[clang][test][NFC] Explicitly specify clang ABI in AST Dumper test Clang <= 4 used the pre-C++11 rule about which structures can be passed in registers. llvm-svn: 364690
2019-06-28 22:37:31 +00:00
// RUN: %clang_cc1 -triple x86_64-unknown-unknown -fclang-abi-compat=7.0 -std=c++17 -ast-dump=json %s | FileCheck %s
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
void f() {
auto IsNotGenericLambda = [](){};
auto IsGenericLambda = [](auto){};
}
struct CanPassInRegisters {
CanPassInRegisters(const CanPassInRegisters&) = default;
};
struct CantPassInRegisters {
CantPassInRegisters(const CantPassInRegisters&) = delete;
};
struct IsEmpty {
};
struct IsNotEmpty {
int a;
};
struct IsAggregate {
int a;
};
struct IsNotAggregate {
private:
int a;
};
struct IsStandardLayout {
void f();
};
struct IsNotStandardLayout {
virtual void f();
};
struct IsTriviallyCopyable {
};
struct IsNotTriviallyCopyable {
IsNotTriviallyCopyable(const IsNotTriviallyCopyable&) {}
};
struct IsPOD {
int a;
};
struct IsNotPOD {
int &a;
};
struct IsTrivial {
IsTrivial() = default;
};
struct IsNotTrivial {
IsNotTrivial() {}
};
struct IsPolymorphic {
virtual void f();
};
struct IsNotPolymorphic {
void f();
};
struct IsAbstract {
virtual void f() = 0;
};
struct IsNotAbstract {
virtual void f();
};
struct IsLiteral {
~IsLiteral() = default;
};
struct IsNotLiteral {
~IsNotLiteral() {}
};
struct HasUserDeclaredConstructor {
HasUserDeclaredConstructor() {}
};
struct HasNoUserDeclaredConstructor {
};
struct HasConstexprNonCopyMoveConstructor {
constexpr HasConstexprNonCopyMoveConstructor() {}
};
struct HasNoConstexprNonCopyMoveConstructor {
HasNoConstexprNonCopyMoveConstructor() {}
};
struct HasMutableFields {
mutable int i;
};
struct HasNoMutableFields {
int i;
};
struct HasVariantMembers {
union {
int i;
};
};
struct HasNoVariantMembers {
};
struct AllowsConstDefaultInit {
int i = 12;
};
struct DoesNotAllowConstDefaultInit {
int i;
};
Add an automated note to files produced by gen_ast_dump_json_test.py. This also details what filters, if any, were used to generate the test output. Updates all the current JSON testing files to include the automated note. llvm-svn: 364055
2019-06-21 14:37:39 +00:00
// NOTE: CHECK lines have been autogenerated by gen_ast_dump_json_test.py
// using --filters=CXXRecordDecl
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 13:22:35 +00:00
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__NSConstantString_tag"
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__va_list_tag"
// CHECK-NEXT: }
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLambda": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 160,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 32,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 162,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 34,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "operator()",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZZ1fvENK3$_0clEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void () const"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 161,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 162,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 34,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConversionDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 162,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 34,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator void (*)()",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZZ1fvENK3$_0cvPFvvEEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (*() const noexcept)()"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 162,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 34,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__invoke",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZZ1fvEN3$_08__invokeEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "storageClass": "static",
// CHECK-NEXT: "inline": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "~",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZZ1fvEN3$_0D1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void () noexcept"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isGenericLambda": true,
// CHECK-NEXT: "isLambda": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "operator()",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "offset": 193,
// CHECK-NEXT: "col": 29,
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 197,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "operator()",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto (auto) const"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 197,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 193,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 193,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 198,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 34,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator auto (*)(type-parameter-0-0)",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "offset": 193,
// CHECK-NEXT: "col": 29,
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConversionDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator auto (*)(type-parameter-0-0)",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto (*() const noexcept)(auto)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__invoke",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "offset": 193,
// CHECK-NEXT: "col": 29,
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
Revert "[Concepts] Placeholder constraints and abbreviated templates" This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac. Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures. Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio Stack trace: ``` ==57032==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19 #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&, clang::AutoType const&, clang::AutoTypeLoc, clang::QualType) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56 #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11 #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*, clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10 #4 0xba38332 in clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*, clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*, clang::SourceRange, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7 #5 0xba3a8a9 in clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool, clang::Expr*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26 #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*, clang::Expr*, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9 #7 0xb39c498 in clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17 #8 0xb394d80 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21 #9 0xb383bbf in clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10 #10 0xb383129 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h #11 0xb53a388 in clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13 #12 0xb539309 in clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20 #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11 #14 0xb559529 in clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21 #15 0xb33c13e in clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10 #16 0xb394703 in clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11 #17 0xb338e52 in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10 #18 0xb337674 in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12 #19 0xb334a96 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12 #20 0xb32f12a in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12 #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20 #22 0x80263f0 in clang::FrontendAction::Execute() /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8 #23 0x7f2a257 in clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33 #24 0x8288bef in clang::ExecuteCompilerInvocation(clang::CompilerInstance*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25 #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*, void*) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15 #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>) /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12 #27 0xacc9fd in main /b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12 #28 0x7f7d82cdb2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0) #29 0xa4dde9 in _start (/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9) ```
2020-01-23 10:38:59 +01:00
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 199,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 35,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__invoke",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto (auto)"
// CHECK-NEXT: },
// CHECK-NEXT: "storageClass": "static",
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 197,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 193,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 193,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 29,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 190,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "~",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZZ1fvEN3$_1D1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void () noexcept"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 212,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 8,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 205,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 292,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 10,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "CanPassInRegisters",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "trivial": true,
// CHECK-NEXT: "userDeclared": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 212,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 8,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 205,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 212,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "CanPassInRegisters",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 235,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 9,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 235,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 289,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 57,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "CanPassInRegisters",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN18CanPassInRegistersC1ERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (const CanPassInRegisters &)"
// CHECK-NEXT: },
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 279,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 47,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 254,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 22,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 278,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 46,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const CanPassInRegisters &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 303,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 12,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 296,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 385,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 14,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "CantPassInRegisters",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "trivial": true,
// CHECK-NEXT: "userDeclared": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 303,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 12,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 296,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 303,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "CantPassInRegisters",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 327,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 13,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 327,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 382,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 58,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "CantPassInRegisters",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN19CantPassInRegistersC1ERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (const CantPassInRegisters &)"
// CHECK-NEXT: },
// CHECK-NEXT: "explicitlyDeleted": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 373,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 49,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 347,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 23,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 372,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 48,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const CantPassInRegisters &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 396,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 16,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 389,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 406,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 17,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsEmpty",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 396,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 16,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 389,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 396,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsEmpty",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 417,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 19,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 410,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 439,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 21,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotEmpty",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 417,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 19,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 410,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 417,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotEmpty",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 436,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 20,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 432,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 436,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 450,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 23,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 11
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 443,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 473,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 25,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsAggregate",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 450,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 23,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 11
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 443,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 450,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 11
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsAggregate",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 470,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 24,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 466,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 470,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 484,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 27,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 14
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 477,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 519,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 30,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotAggregate",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 484,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 27,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 14
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 477,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 484,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 14
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotAggregate",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "AccessSpecDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 501,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 28,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 501,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 508,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "access": "private"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 516,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 29,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 512,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 516,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 530,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 32,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 523,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 561,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 34,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsStandardLayout",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 530,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 32,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 523,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 530,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsStandardLayout",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 556,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 33,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 551,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 558,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN16IsStandardLayout1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 36,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 565,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 614,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 38,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotStandardLayout",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPolymorphic": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 36,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 565,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotStandardLayout",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 609,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 37,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 596,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 611,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN19IsNotStandardLayout1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "virtual": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 36,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN19IsNotStandardLayoutaSERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotStandardLayout &(const IsNotStandardLayout &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const IsNotStandardLayout &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN19IsNotStandardLayoutaSEOS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotStandardLayout &(IsNotStandardLayout &&)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotStandardLayout &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 572,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~IsNotStandardLayout",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN19IsNotStandardLayoutD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 625,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 40,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 618,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 647,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 41,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsTriviallyCopyable",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 625,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 40,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 618,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 625,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsTriviallyCopyable",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 658,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 43,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 651,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 742,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 45,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotTriviallyCopyable",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userDeclared": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 658,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 43,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 651,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 658,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "IsNotTriviallyCopyable",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 685,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 44,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 685,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 740,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 58,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotTriviallyCopyable",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN22IsNotTriviallyCopyableC1ERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (const IsNotTriviallyCopyable &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 737,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 55,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 708,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 26,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 736,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 54,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const IsNotTriviallyCopyable &"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 739,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 57,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 740,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 58,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 753,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 47,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 746,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 770,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 49,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsPOD",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 753,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 47,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 746,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 753,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsPOD",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 767,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 48,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 763,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 767,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 781,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 51,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 8
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 774,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 802,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 53,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotPOD",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 781,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 51,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 8
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 774,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 781,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 8
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotPOD",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 799,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 52,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 794,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 799,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 813,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 55,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 806,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 850,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 57,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsTrivial",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 813,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 55,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 806,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 813,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "IsTrivial",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 827,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 56,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 827,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 847,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 23,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsTrivial",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN9IsTrivialC1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 861,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 59,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 854,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 896,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 61,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotTrivial",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userProvided": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 861,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 59,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 854,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 861,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "IsNotTrivial",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 878,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 60,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 878,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 894,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 19,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotTrivial",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN12IsNotTrivialC1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 893,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 894,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 19,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 63,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 900,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 943,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 65,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsPolymorphic",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPolymorphic": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 63,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 900,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsPolymorphic",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 938,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 64,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 925,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 940,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsPolymorphic1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "virtual": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 63,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsPolymorphicaSERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsPolymorphic &(const IsPolymorphic &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const IsPolymorphic &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsPolymorphicaSEOS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsPolymorphic &(IsPolymorphic &&)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsPolymorphic &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 907,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~IsPolymorphic",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsPolymorphicD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 954,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 67,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 947,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 985,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 69,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotPolymorphic",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 954,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 67,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 947,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 954,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotPolymorphic",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 980,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 68,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 975,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 4
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 982,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN16IsNotPolymorphic1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 71,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 989,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1033,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 73,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsAbstract",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAbstract": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPolymorphic": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 71,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 989,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsAbstract",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1024,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 72,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1011,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1030,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 22,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN10IsAbstract1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "virtual": true,
// CHECK-NEXT: "pure": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 71,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN10IsAbstractaSERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsAbstract &(const IsAbstract &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const IsAbstract &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN10IsAbstractaSEOS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsAbstract &(IsAbstract &&)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsAbstract &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 996,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 10
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~IsAbstract",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN10IsAbstractD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 75,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1037,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1080,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 77,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotAbstract",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPolymorphic": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 75,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1037,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "IsNotAbstract",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1075,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 76,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1062,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1077,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsNotAbstract1fEv",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "virtual": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 75,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsNotAbstractaSERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotAbstract &(const IsNotAbstract &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const IsNotAbstract &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsNotAbstractaSEOS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotAbstract &(IsNotAbstract &&)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "IsNotAbstract &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1044,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 13
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~IsNotAbstract",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN13IsNotAbstractD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1091,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 79,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1084,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1129,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 81,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsLiteral",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "trivial": true,
// CHECK-NEXT: "userDeclared": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1091,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 79,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1084,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1091,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "IsLiteral",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1105,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 80,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1105,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1126,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 24,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "~IsLiteral",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN9IsLiteralD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1140,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 83,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1133,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1176,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 85,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "IsNotLiteral",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userDeclared": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "moveAssign": {},
// CHECK-NEXT: "moveCtor": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1140,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 83,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1133,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1140,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 12
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "IsNotLiteral",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1157,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 84,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1157,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1174,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "~IsNotLiteral",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN12IsNotLiteralD1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void () noexcept"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1173,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 19,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1174,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1187,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 87,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 26
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1180,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1250,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 89,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasUserDeclaredConstructor",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userProvided": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1187,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 87,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 26
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1180,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1187,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 26
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "HasUserDeclaredConstructor",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1218,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 88,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 26
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1218,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 26
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1248,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasUserDeclaredConstructor",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN26HasUserDeclaredConstructorC1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1247,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 32,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1248,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1261,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 91,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1254,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1292,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 92,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasNoUserDeclaredConstructor",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1261,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 91,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1254,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1261,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasNoUserDeclaredConstructor",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1303,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 94,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 34
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1296,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1392,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 96,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasConstexprNonCopyMoveConstructor",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userProvided": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1303,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 94,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 34
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1296,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1303,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 34
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "HasConstexprNonCopyMoveConstructor",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1352,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 95,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 34
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1342,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 9
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1390,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 51,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasConstexprNonCopyMoveConstructor",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN34HasConstexprNonCopyMoveConstructorC1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1389,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 50,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1390,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 51,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1403,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 98,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 36
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1396,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1486,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 100,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasNoConstexprNonCopyMoveConstructor",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "userProvided": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasUserDeclaredConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1403,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 98,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 36
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1396,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1403,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 36
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "HasNoConstexprNonCopyMoveConstructor",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1444,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 99,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 36
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1444,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 36
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1484,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 43,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasNoConstexprNonCopyMoveConstructor",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN36HasNoConstexprNonCopyMoveConstructorC1Ev",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1483,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 42,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1484,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 43,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 102,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1490,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1533,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 104,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasMutableFields",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsOverloadResolution": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsOverloadResolution": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasMutableFields": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 102,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1490,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasMutableFields",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1530,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 103,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 15,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1518,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 7
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1530,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 15,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
// CHECK-NEXT: "mutable": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXConstructorDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 102,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasMutableFields",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN16HasMutableFieldsC1ERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (const HasMutableFields &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const HasMutableFields &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "operator=",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 12:33:16 +00:00
// CHECK-NEXT: "mangledName": "_ZN16HasMutableFieldsaSERKS_",
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "HasMutableFields &(const HasMutableFields &)"
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1497,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 16
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const HasMutableFields &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1544,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 106,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1537,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1574,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 108,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasNoMutableFields",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1544,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 106,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1537,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1544,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 18
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasNoMutableFields",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1571,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 107,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1567,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1571,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1585,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 110,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 17
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1578,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1631,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 114,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasVariantMembers",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasVariantMembers": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1585,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 110,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 17
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1578,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1585,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 17
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasVariantMembers",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1607,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 111,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1607,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1628,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 113,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "union",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasVariantMembers": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1623,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 112,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 9,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1619,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 5,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1623,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 9,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1607,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 111,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1607,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1607,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 5
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "HasVariantMembers::(anonymous union at {{.*}}:111:3)"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1623,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 112,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 9,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1623,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 9,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1623,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 9,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "i"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1642,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 116,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1635,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1664,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 117,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "HasNoVariantMembers",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1642,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 116,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1635,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1642,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 19
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "HasNoVariantMembers",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1675,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 119,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1668,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1714,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 121,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "AllowsConstDefaultInit",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1675,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 119,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1668,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1675,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 22
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "AllowsConstDefaultInit",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1706,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 120,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1702,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1710,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 2
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
// CHECK-NEXT: "hasInClassInitializer": true,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1710,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 2
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1710,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 2
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
// CHECK-NEXT: "valueCategory": "rvalue",
// CHECK-NEXT: "value": "12"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1725,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 123,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1718,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1765,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 125,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "DoesNotAllowConstDefaultInit",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1725,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 123,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1718,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 6
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1725,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 28
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "DoesNotAllowConstDefaultInit",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
// CHECK-NEXT: "loc": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1762,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "line": 124,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1758,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 3
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
Add more information to JSON AST dumping of source locations. This adds information about the offset within the source file to the given source location as well as information about the include file a location is from. These pieces of information allow for more efficient post-processing of JSON AST dumps. llvm-svn: 374921
2019-10-15 17:30:19 +00:00
// CHECK-NEXT: "offset": 1762,
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: "col": 7,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-24 20:07:11 +00:00
// CHECK-NEXT: "tokLen": 1
Add test cases for dumping record definition data to JSON; NFC. llvm-svn: 363849
2019-06-19 17:49:25 +00:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
Reference in New Issue Copy Permalink