Home
last modified time | relevance | path

Searched refs:parsing (Results 1 – 25 of 1451) sorted by relevance

12345678910>>...59

/external/llvm-project/llvm/test/tools/llvm-rc/
Dparser.test105 ; PSTRINGTABLE1: llvm-rc: Error parsing file: expected string, got }
110 ; PSTRINGTABLE2: llvm-rc: Error parsing file: expected optional statement type, BEGIN or '{', got …
115 ; PEOF: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got <EOF>
120 ; PCHARACTERISTICS1: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got BEGIN
125 ; PNONSENSE1: llvm-rc: Error parsing file: expected int or identifier, got &
130 ; PNONSENSE2: llvm-rc: Error parsing file: expected filename, '{' or BEGIN, got <EOF>
135 ; PNONSENSE3: llvm-rc: Error parsing file: expected int or identifier, got <EOF>
140 ; PLANGUAGE1: llvm-rc: Error parsing file: expected ',', got 7
145 ; PLANGUAGE2: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got ,
150 ; PHTML2: llvm-rc: Error parsing file: expected string, got ,
[all …]
Dparser-expr.test22 ; BINARY1: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got &
27 ; BINARY2: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got |
32 ; BINARY3: llvm-rc: Error parsing file: expected '-', '~', integer or '(', got +
37 ; UNARY: llvm-rc: Error parsing file: expected ',', got ~
42 ; UNBALANCED1: llvm-rc: Error parsing file: expected ')', got ,
47 ; UNBALANCED2: llvm-rc: Error parsing file: expected ',', got )
52 ; UNBALANCED3: llvm-rc: Error parsing file: expected ',', got )
/external/llvm-project/flang/tools/f18-parse-demo/
Df18-parse-demo.cpp164 Fortran::parser::Parsing parsing{allCookedSources}; in CompileFortran() local
167 parsing.Prescan(path, options); in CompileFortran()
168 if (!parsing.messages().empty() && in CompileFortran()
169 (driver.warningsAreErrors || parsing.messages().AnyFatalError())) { in CompileFortran()
171 parsing.messages().Emit(llvm::errs(), parsing.allCooked()); in CompileFortran()
176 parsing.DumpProvenance(llvm::outs()); in CompileFortran()
180 parsing.DumpCookedChars(llvm::outs()); in CompileFortran()
183 parsing.Parse(llvm::outs()); in CompileFortran()
194 parsing.ClearLog(); in CompileFortran()
195 parsing.messages().Emit(llvm::errs(), parsing.allCooked()); in CompileFortran()
[all …]
/external/llvm-project/flang/tools/f18/
Df18.cpp208 Fortran::parser::Parsing parsing{allCookedSources}; in CompileFortran() local
209 parsing.Prescan(path, options); in CompileFortran()
210 if (!parsing.messages().empty() && in CompileFortran()
211 (driver.warningsAreErrors || parsing.messages().AnyFatalError())) { in CompileFortran()
213 parsing.messages().Emit(llvm::errs(), allCookedSources); in CompileFortran()
218 parsing.DumpProvenance(llvm::outs()); in CompileFortran()
222 parsing.messages().Emit(llvm::errs(), allCookedSources); in CompileFortran()
223 parsing.DumpCookedChars(llvm::outs()); in CompileFortran()
226 parsing.Parse(llvm::outs()); in CompileFortran()
228 parsing.DumpParsingLog(llvm::outs()); in CompileFortran()
[all …]
/external/llvm-project/llvm/test/tools/llvm-dwarfdump/X86/
Ddebug_line_invalid.test1 ## Test the different error cases in the debug line parsing and how they prevent
4 ## Show that a bad length stops parsing of the section.
12 ## parsing can continue.
20 ## Show that non-fatal errors do not prevent parsing the rest of the section.
57 # RESERVED: warning: parsing line table prologue at offset 0x00000048: unsupported reserved unit le…
71 # SOME-ERR-NEXT: warning: parsing line table prologue at offset 0x00000048: unsupported version 0
80 # SOME-ERR-NEXT: warning: parsing line table prologue at offset 0x0000004e: unsupported version 1
84 # SOME-ERR-NEXT: warning: parsing line table prologue at 0x00000054 found an invalid directory or f…
95 # SOME-ERR-NEXT: warning: parsing line table prologue at 0x00000081 found an invalid directory or f…
108 # SOME-ERR-NEXT: warning: unknown data in line table prologue at offset 0x000000c7: parsing ended (…
[all …]
Ddebug_pub_tables_error_cases.s48 # ERR: error: name lookup table at offset 0x1b parsing failed: unexpected end of data at offset 0x2…
60 # ERR: error: name lookup table at offset 0x29 parsing failed: unexpected end of data at offset 0x3…
73 # ERR: error: name lookup table at offset 0x3a parsing failed: unexpected end of data at offset 0x4…
86 # ERR: error: name lookup table at offset 0x4c parsing failed: no null terminated string at offset …
100 # ERR: error: name lookup table at offset 0x5f parsing failed: no null terminated string at offset …
134 # ERR: error: name lookup table at offset 0x91 parsing failed: unexpected end of data at offset 0x9…
139 # ERR-MIN-NEXT: error: name lookup table at offset 0x0 parsing failed: unexpected end of data at of…
141 # ERR-MIN-NEXT: error: name lookup table at offset 0x0 parsing failed: unexpected end of data at of…
143 # ERR-MIN-NEXT: error: name lookup table at offset 0x0 parsing failed: unexpected end of data at of…
Ddebug_line_short_prologue.s1 ## Test cases when we run into the end of section while parsing a line table
17 # C0-NEXT: warning: parsing line table prologue at 0x00000000 found an invalid directory or file t…
19 # C1-NEXT: warning: parsing line table prologue at 0x00000000 found an invalid directory or file t…
21 # C2-NEXT: warning: parsing line table prologue at 0x00000000 found an invalid directory or file t…
/external/python/pycparser/
DCHANGES3 - #61: Fix slow backtracking when parsing strings.
7 - #314: Fix failed parsing of unnamed function parameters with array dim
13 - #363: Fix incorrect AST when parsing offsetof.
17 - PR #277: Fix parsing of floating point literals
18 - PR #254: Add support for parsing empty structs
45 - Issue #117: Fix parsing of extra semi-colons inside structure declarations.
47 - PR #101: Added support for parsing pragmas into the AST.
57 - Added CParser parameter to specify output directory for generated parsing
68 - Added a bunch more fake headers and typedefs to support parsing C projects
124 - Issue #83: fix parsing and C generation to distinguish between initializer
[all …]
/external/rust/crates/syn/
DCargo.toml.orig24 default = ["derive", "parsing", "printing", "clone-impls", "proc-macro"]
27 parsing = []
58 required-features = ["full", "parsing"]
62 required-features = ["full", "parsing"]
DCargo.toml36 required-features = ["full", "parsing"]
40 required-features = ["full", "parsing"]
88 default = ["derive", "parsing", "printing", "clone-impls", "proc-macro"]
93 parsing = []
/external/llvm-project/clang-tools-extra/docs/clang-tidy/checks/
Dmodernize-pass-by-value.rst120 Note about delayed template parsing
123 When delayed template parsing is enabled, constructors part of templated
126 template parsing is enabled by default on Windows as a Microsoft extension:
129 Delayed template parsing can be enabled using the `-fdelayed-template-parsing`
130 flag and disabled using `-fno-delayed-template-parsing`.
140 = // using -fdelayed-template-parsing (default on Windows)
143 + // using -fno-delayed-template-parsing (default on non-Windows systems)
/external/libwebm/webm_parser/
DREADME.md8 and `SimpleTag`. It supports incremental parsing; parsing may be stopped at any
10 WebM element, so parsing need not start from the beginning of the file.
51 situation, the parser will stop parsing and return the status it received.
55 available, it should return `Status::kEndOfFile`. This will cause parsing to
64 element(s)), and the parser is parsing them and hits end-of-file, the parser may
66 already reported `Status::kEndOfFile`) as nested parsers terminate parsing.
81 notifies the `Callback` implementation as objects complete parsing. For some
165 to allow parsing to continue. If you would like parsing to stop, return any
168 If you return a non-parsing-error status code (.e.g. `Status::kOkPartial`,
169 `Status::kWouldBlock`, etc. or your own status code with a value > 0), parsing
[all …]
/external/python/cpython3/Doc/library/
Dxml.sax.handler.rst33 This interface specifies only those DTD events required for basic parsing
60 | access: (parsing) read-only; (not parsing) read/write
70 | access: (parsing) read-only; (not parsing) read/write
79 | access: (parsing) read-only; (not parsing) read/write
88 | access: (parsing) read-only; (not parsing) read/write
96 | access: (parsing) read-only; (not parsing) read/write
106 | access: (parsing) read-only; (not parsing) read/write
136 | description: When parsing, the current DOM node being visited if this is
137 a DOM iterator; when not parsing, the root DOM node for iteration.
138 | access: (parsing) read-only; (not parsing) read/write
[all …]
Durllib.rst14 * :mod:`urllib.parse` for parsing URLs
15 * :mod:`urllib.robotparser` for parsing ``robots.txt`` files
/external/python/cpython2/Doc/library/
Dxml.sax.handler.rst32 This interface specifies only those DTD events required for basic parsing
59 | access: (parsing) read-only; (not parsing) read/write
69 | access: (parsing) read-only; (not parsing) read/write
78 | access: (parsing) read-only; (not parsing) read/write
87 | access: (parsing) read-only; (not parsing) read/write
95 | access: (parsing) read-only; (not parsing) read/write
105 | access: (parsing) read-only; (not parsing) read/write
135 | description: When parsing, the current DOM node being visited if this is
136 a DOM iterator; when not parsing, the root DOM node for iteration.
137 | access: (parsing) read-only; (not parsing) read/write
[all …]
/external/ply/ply/
DANNOUNCE8 common parsing tools lex and yacc. PLY-3.11 is a minor bug fix
26 - Parsing is based on LR-parsing which is fast, memory efficient,
28 properties when dealing with syntax errors and other parsing
29 problems. Currently, PLY can build its parsing tables using
/external/llvm/test/Object/
Dcorrupt.test5 SECNAME: Error reading file: Invalid data was encountered while parsing the file.
12 SECDATA: Error reading file: Invalid data was encountered while parsing the file.
19 SYMNAME: Error reading file: Invalid data was encountered while parsing the file.
65 DYN-TABLE-OFFSET: Invalid data was encountered while parsing the file.
72 DYN-TABLE-TOO-LARGE: Invalid data was encountered while parsing the file.
/external/llvm/test/tools/llvm-objdump/
Dmalformed-archives.test8 # bogus1: Invalid data was encountered while parsing the file
14 # bogus2: LLVM ERROR: Invalid data was encountered while parsing the file
20 # bogus3: LLVM ERROR: Invalid data was encountered while parsing the file
/external/protobuf/objectivec/Tests/
DGPBPerfTests.m68 // This and the next test are meant to monitor that the parsing functionality of protos does not
69 // lock across threads when parsing different instances. The Serial version of the test should run
70 // around ~2 times slower than the Parallel version since it's parsing the protos in the same
85 // This and the previous test are meant to monitor that the parsing functionality of protos does
86 // not lock across threads when parsing different instances. The Serial version of the test should
87 // run around ~2 times slower than the Parallel version since it's parsing the protos in the same
117 // This and the next test are meant to monitor that the parsing functionality of protos does not
118 // lock across threads when parsing different instances when using extensions. The Serial version
119 // of the test should run around ~2 times slower than the Parallel version since it's parsing the
138 // This and the previous test are meant to monitor that the parsing functionality of protos does
[all …]
/external/python/cpython2/Misc/NEWS.d/next/Core and Builtins/
D2018-05-25-18-20-04.bpo-33645.GYGIPH.rst1 Fixed an "unknown parsing error" on parsing the "<>" operator when run
/external/selinux/python/sepolgen/
DHACKING50 /usr/share/selinux/devel/include. This uses the LGPL parsing library
53 switch to a more powerful parsing library in the future, but for now
59 Infrastructure for parsing SELinux related messages as produced by the
60 audit system. This is not a general purpose audit parsing library - it
68 deliberately only loosely coupled to the audit parsing to allow
/external/llvm-project/lldb/test/Shell/SymbolFile/Breakpad/
Dstack-cfi-parsing.test1 # RUN: yaml2obj %S/Inputs/stack-cfi-parsing.yaml -o %t
2 # RUN: %lldb -c %t -o "target symbols add %S/Inputs/stack-cfi-parsing.syms" \
14 # CHECK-NEXT: Address range of this UnwindPlan: [stack-cfi-parsing.out..module_image + 0-0x00000000…
51 # CHECK: Address range of this UnwindPlan: [stack-cfi-parsing.out..module_image + 9-0x0000000000000…
/external/dynamic_depth/internal/dynamic_depth/
DREADME.md1 # dynamic\_depth - A library for parsing and writing Dynamic Depth metadata
3 dynamic\_depth is a portable library for parsing and writing Dynamic Depth
/external/curl/tests/data/
Dtest201770 Metalink: parsing (file://%PWD/log/test2017.metalink) metalink/XML...
71 Metalink: parsing (file://%PWD/log/test2017.metalink) WARNING (missing or invalid file name)
72 Metalink: parsing (file://%PWD/log/test2017.metalink) FAILED
Dtest201970 Metalink: parsing (file://%PWD/log/test2019.metalink) metalink/XML...
71 Metalink: parsing (file://%PWD/log/test2019.metalink) WARNING (missing or invalid file name)
72 Metalink: parsing (file://%PWD/log/test2019.metalink) FAILED

12345678910>>...59