Home
last modified time | relevance | path

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

12345678910>>...14

/llvm-project/llvm/test/tools/llvm-rc/
H A 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 …]
H A 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 )
/llvm-project/flang/tools/f18-parse-demo/
H A Df18-parse-demo.cpp166 Fortran::parser::Parsing parsing{allCookedSources}; in CompileFortran() local
169 parsing.Prescan(path, options); in CompileFortran()
170 if (!parsing.messages().empty() && in CompileFortran()
171 (driver.warningsAreErrors || parsing.messages().AnyFatalError())) { in CompileFortran()
173 parsing.messages().Emit(llvm::errs(), parsing.allCooked()); in CompileFortran()
178 parsing.DumpProvenance(llvm::outs()); in CompileFortran()
182 parsing.messages().Emit(llvm::errs(), allCookedSources); in CompileFortran()
184 parsing.DumpCookedChars(llvm::outs()); in CompileFortran()
186 parsing.EmitPreprocessedSource(llvm::outs(), driver.lineDirectives); in CompileFortran()
190 parsing.Parse(llvm::outs()); in CompileFortran()
[all …]
/llvm-project/flang/tools/bbc/
H A Dbbc.cpp38 #include "flang/Parser/parsing.h"
316 Fortran::parser::Parsing parsing{semanticsContext.allCookedSources()}; in convertFortranSourceToMLIR()
317 parsing.Prescan(path, options); in convertFortranSourceToMLIR()
318 if (!parsing.messages().empty() && (parsing.messages().AnyFatalError())) { in convertFortranSourceToMLIR()
320 parsing.messages().Emit(llvm::errs(), parsing.allCooked()); in convertFortranSourceToMLIR()
325 parsing.Parse(llvm::outs()); in convertFortranSourceToMLIR()
326 if (!parsing.consumedWholeFile()) { in convertFortranSourceToMLIR()
327 parsing in convertFortranSourceToMLIR()
296 Fortran::parser::Parsing parsing{semanticsContext.allCookedSources()}; convertFortranSourceToMLIR() local
[all...]
/llvm-project/llvm/test/tools/llvm-dwarfdump/X86/
H A 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 …]
H A 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…
H A 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…
H A Ddebug_line_short_prologue_v4.s1 ## Test cases when we run into the end of section while parsing a line table
24 # C0-NEXT: warning: parsing line table prologue at 0x00000000 found an invalid directory or file t…
28 # C1-NEXT: warning: parsing line table prologue at 0x00000000 found an invalid directory or file t…
/llvm-project/flang/examples/FlangOmpReport/
H A DFlangOmpReport.cpp54 Parsing &parsing = getParsing(); in executeAction() local
56 visitor.parsing = &parsing; in executeAction()
59 Walk(parsing.parseTree(), visitor); in executeAction()
H A DFlangOmpReportVisitor.cpp62 return parsing->allCooked().GetSourcePositionRange(o.source)->first; in getLocation()
70 return parsing->allCooked().GetSourcePositionRange(c.source)->first; in getLocation()
77 return (parsing->allCooked().GetSourcePositionRange(source))->first; in getLocation()
83 return parsing->allCooked() in getLocation()
91 return (parsing->allCooked().GetSourcePositionRange(source))->first; in getLocation()
95 return (parsing->allCooked().GetSourcePositionRange(source))->first;
/llvm-project/clang/tools/clang-installapi/
H A DInstallAPIOpts.td13 // Include the common option parsing interfaces.
52 HelpText<"Add additional project header location for parsing">;
57 HelpText<"Exclude project header from parsing">;
62 HelpText<"Add additional public header location for parsing">;
67 HelpText<"Add additional private header location for parsing">;
72 HelpText<"Exclude public header from parsing">;
77 HelpText<"Exclude private header from parsing">;
127 MetaVarName<"<file>">, HelpText<"Include file before parsing, can only be used with -Xproject">;
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/modernize/
H A Dpass-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)
/llvm-project/mlir/test/IR/
H A Dinvalid-custom-print-parse.mlir4 // expected-error@+1 {{custom op 'test.custom_dimension_list_attr' Failed parsing dimension list.}}
9 // expected-error@+1 {{custom op 'test.custom_dimension_list_attr' Failed parsing dimension list. D…
15 // expected-error@+1 {{custom op 'test.custom_dimension_list_attr' Failed parsing dimension list.}}
/llvm-project/llvm/test/TableGen/
H A DListSlices-fail.td10 // ERR0: [[FILE]]:[[@LINE+1]]:26: error: Unknown or reserved token when parsing a value
16 // ERR1: [[FILE]]:[[@LINE+1]]:26: error: Unknown or reserved token when parsing a value
58 // ERR8: [[FILE]]:[[@LINE+1]]:26: error: Unknown or reserved token when parsing a value
64 // ERR9: [[FILE]]:[[@LINE+1]]:32: error: Unknown or reserved token when parsing a value
H A Dforeach-range-parse-errors0.td13 // CHECK-NOT: error: Unknown or reserved token when parsing a value
14 // CHECK: [[FILE]]:[[@LINE+3]]:22: error: Unknown or reserved token when parsing a value
H A Dpaste-reserved.td12 // ERROR1: error: Unknown or reserved token when parsing a value
21 // ERROR2: error: Unknown or reserved token when parsing a value
H A DMultiClass-defm.td32 // This used to throw an error during multiclass parsing as NAME was not
33 // recognized when parsing the template arguments.
/llvm-project/lldb/test/Shell/SymbolFile/Breakpad/
H A 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…
/llvm-project/clang/docs/
H A DMSVCCompatibility.rst34 parsing and semantic compatibility tweaks are controlled by
35 ``-fms-compatibility`` and ``-fdelayed-template-parsing``, and they are a work
120 The first major semantic difference is that MSVC appears to defer all parsing
123 controlled by the ``-fdelayed-template-parsing`` flag. While Clang delays
124 parsing of method bodies, it still parses the bodies *before* template argument
132 is parsing your template, so the user is sometimes required to use the
135 user intended to find the name in a dependent base. While parsing the
155 application. There are still issues parsing WRL headers for modern Windows 8
/llvm-project/mlir/test/Bytecode/
H A Dbytecode_callback.mlir11 // VERSION_1_2: Overriding parsing of IntegerType encoding...
14 // VERSION_2_0-NOT: Overriding parsing of IntegerType encoding...
/llvm-project/polly/lib/External/isl/
H A DChangeLog34 - accept ranges in tuples during parsing
189 - improved argument parsing
197 - improved parsing
217 - improved parsing
231 - improved argument parsing
255 - improved argument parsing
/llvm-project/llvm/test/Assembler/
H A Dthinlto-bad-summary3.ll1 ; Test that we get appropriate error when parsing summary with unbalanced
5 ; CHECK: error: found end of file while parsing summary entry
/llvm-project/llvm/test/DebugInfo/
H A Dtypeunit-header.test3 This is testing a bugfix where parsing the type unit header was not
9 We make sure that llvm-dwarfdump is parsing the type unit header correctly
/llvm-project/clang/test/Parser/
H A Dobjc-at-directive-fixit.m11 // Provide a fixit when we are parsing a standalone statement
19 // Ensure that no fixit is given when parsing expressions
/llvm-project/llvm/test/tools/llvm-objdump/XCOFF/
H A Ddisassemble-invalid-traceback-table.test1 ## Test that parsing of an invalid XCOFF traceback table with a too
27 # WARN: warning: '[[FILE]]': failure parsing traceback table with address: 0x4

12345678910>>...14