maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/AST/ast-dump-records-json.cpp

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

4257 lines
130 KiB
C++
Raw Normal View History

Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// RUN: %clang_cc1 -triple x86_64-unknown-unknown -std=c++17 -ast-dump=json %s | FileCheck %s
struct A;
struct B;
struct A {
int a;
int b, c;
int d : 12;
int : 0;
int e : 10;
B *f;
};
struct C {
struct {
int a;
} b;
union {
int c;
float d;
};
struct {
int e, f;
};
};
struct D {
int a;
int b[10];
int c[];
};
union E;
union F;
union E {
int a;
int b, c;
int d : 12;
int : 0;
int e : 10;
B *f;
};
union G {
struct {
int a;
} b;
union {
int c;
float d;
};
struct {
int e, f;
};
};
struct Base1 {};
struct Base2 {};
struct Base3 {};
struct Derived1 : Base1 {
};
struct Derived2 : private Base1 {
};
struct Derived3 : virtual Base1 {
};
struct Derived4 : Base1, virtual Base2, protected Base3 {
};
struct Derived5 : protected virtual Base1 {
};
template <typename... Bases>
struct Derived6 : virtual public Bases... {
};
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 22:37:39 +08:00
// NOTE: CHECK lines have been autogenerated by gen_ast_dump_json_test.py
// using --filters=CXXRecordDecl
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__NSConstantString_tag"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__va_list_tag"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "file": "{{.*}}",
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 3,
// CHECK-NEXT: "col": 8,
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "A",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 4,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "B",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 6,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 13,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "previousDecl": "0x{{.*}}",
// CHECK-NEXT: "name": "A",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 6,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "A",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 7,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 8,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 9,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "12",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "12"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 10,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "0",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "0"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 11,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "10",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "10"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 12,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "B *"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 15,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 28,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "C",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 15,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "C",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 16,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 18,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 17,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 18,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 16,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 18,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
Modify TypePrinter to differentiate between anonymous struct and unnamed struct Currently TypePrinter lumps anonymous classes and unnamed classes in one group "anonymous" this is not correct and can be confusing in some contexts. Differential Revision: https://reviews.llvm.org/D96807
2021-02-23 01:58:26 +08:00
// CHECK-NEXT: "desugaredQualType": "C::(unnamed struct at {{.*}}:16:3)",
// CHECK-NEXT: "qualType": "struct (unnamed struct at {{.*}}:16:3)"
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 20,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 23,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "union",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 21,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 22,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "float"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 20,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "C::(anonymous union at {{.*}}:20:3)"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 21,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "c"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 22,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "d"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 25,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 27,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 26,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 25,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "C::(anonymous struct at {{.*}}:25:3)"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 26,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "e"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "f"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 30,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 34,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "D",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 30,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "D",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 31,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 32,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
Recommit: Compress formatting of array type names (int [4] -> int[4]) Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc).
2021-10-15 05:52:47 +08:00
// CHECK-NEXT: "qualType": "int[10]"
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 33,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
Recommit: Compress formatting of array type names (int [4] -> int[4]) Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc).
2021-10-15 05:52:47 +08:00
// CHECK-NEXT: "qualType": "int[]"
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 36,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "E",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "union"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 38,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "F",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "union"
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 40,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 47,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "previousDecl": "0x{{.*}}",
// CHECK-NEXT: "name": "E",
// CHECK-NEXT: "tagUsed": "union",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 40,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "E",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "union"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 41,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 42,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 43,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "12",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "12"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 44,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "0",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "0"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 45,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isBitfield": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantExpr",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Fix test/AST/ast-dump-records-json.cpp after ConstantExpr change in D63376 llvm-svn: 364033
2019-06-21 19:39:41 +08:00
// CHECK-NEXT: "value": "10",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IntegerLiteral",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "value": "10"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 46,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "B *"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 49,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 62,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "G",
// CHECK-NEXT: "tagUsed": "union",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 49,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "G",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "union"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 50,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 52,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 51,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 52,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 50,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 52,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
Modify TypePrinter to differentiate between anonymous struct and unnamed struct Currently TypePrinter lumps anonymous classes and unnamed classes in one group "anonymous" this is not correct and can be confusing in some contexts. Differential Revision: https://reviews.llvm.org/D96807
2021-02-23 01:58:26 +08:00
// CHECK-NEXT: "desugaredQualType": "G::(unnamed struct at {{.*}}:50:3)",
// CHECK-NEXT: "qualType": "struct (unnamed struct at {{.*}}:50:3)"
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 54,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 57,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "union",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 55,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "float"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 54,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "G::(anonymous union at {{.*}}:54:3)"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 55,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "c"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "d"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 59,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 61,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 60,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 59,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "G::(anonymous struct at {{.*}}:59:3)"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 60,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "e"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "IndirectFieldDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "name": "f"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 64,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Base1",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Base1",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base1aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1 &(const Base1 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Base1 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base1aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1 &(Base1 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Base1",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base1D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 65,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Base2",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Base2",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base2aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base2 &(const Base2 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Base2 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base2aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base2 &(Base2 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base2 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Base2",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base2D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 66,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Base3",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Base3",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base3aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base3 &(const Base3 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Base3 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base3aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base3 &(Base3 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "constexpr": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base3 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Base3",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN5Base3D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 68,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 69,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived1",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "public",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "none"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 68,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived1",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 71,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 72,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived2",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "private",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "private"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 71,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived2",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 74,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 75,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived3",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "nonTrivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "public",
// CHECK-NEXT: "isVirtual": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "none"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 74,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived3",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived3aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived3 &(const Derived3 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Derived3 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived3aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived3 &(Derived3 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived3 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Derived3",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived3D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 77,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 78,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived4",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "nonTrivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "public",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "none"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "public",
// CHECK-NEXT: "isVirtual": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base2"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "none"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "protected",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base3"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "protected"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 77,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived4",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived4aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived4 &(const Derived4 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Derived4 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived4aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived4 &(Derived4 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived4 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Derived4",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived4D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 80,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 81,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived5",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "nonTrivial": true,
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "nonTrivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "nonTrivial": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "simple": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "protected",
// CHECK-NEXT: "isVirtual": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Base1"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "protected"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 80,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived5",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived5aSERKS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived5 &(const Derived5 &)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "const Derived5 &"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived5aSEOS_",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived5 &(Derived5 &&)"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
// CHECK-NEXT: "explicitlyDefaulted": "default",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Derived5 &&"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXDestructorDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "~Derived5",
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 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_ZN8Derived5D1Ev",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inline": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "explicitlyDefaulted": "default"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 84,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 85,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Derived6",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "definitionData": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "canConstDefaultInit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "copyCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "defaultCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "dtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// 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,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveAssign": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "moveCtor": {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "bases": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "access": "public",
// CHECK-NEXT: "isPackExpansion": true,
// CHECK-NEXT: "isVirtual": true,
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Bases"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "writtenAccess": "public"
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: ],
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-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-25 04:07:11 +08:00
// CHECK-NEXT: "line": 84,
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08: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-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: }
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "Derived6",
Add more tests for AST JSON output; NFC. This adds tests for dumping records and statements. llvm-svn: 361065
2019-05-18 03:14:01 +08:00
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }