Lines Matching +refs:tablegen +refs:mode +refs:syntax +refs:table

150   like ``missing semicolon`` over wording like ``syntax error`` (which is not
322   The parser is very unforgiving.  A syntax error, even whitespace, will abort,
462 semicolon at the end of a statement or a use of deprecated syntax that is
544 mode.  Instead of formatting and printing out the diagnostics, this
548 documentation for the ``-verify`` mode can be found at
668 Option definitions are processed by the ``-gen-opt-parser-defs`` tablegen
703 Next, declare the command line interface of the option in the tablegen file
749 New options are recognized by the ``clang`` driver mode if ``Visibility`` is
838 C++ code with simple, declarative tablegen annotations and it's being used for
847 uses key paths, which are declared in two steps. First, a tablegen definition
866 a string that the tablegen backend uses as a prefix to the
932 How does the tablegen backend know what to put in place of ``[...]`` in the
966 boolean value that's statically unknown in the tablegen file). Then, the key
1130   not reading in "raw" mode) this contains a pointer to the unique hash value
1262 * The lexer can operate in "raw" mode.  This mode has several features that
1265   This mode is used for lexing within an "``#if 0``" block, for example.
1267   support the ``-C`` preprocessor mode, which passes comments through, and is
1269 * The lexer can be in ``ParsingFilename`` mode, which happens when
1270   preprocessing after reading a ``#include`` directive.  This mode changes the
1274   ``ParsingPreprocessorDirective`` mode is entered.  This changes the parser to
1406 Some AST nodes (for example, ``ParenExpr``) represent only syntax, and others
1408 will represent a combination of syntax and associated semantics. Inheritance
1696   number of declarations) or hash table (for declaration contexts with more
1936 maintaining the lookup table used for the semantics-centric view.  Given a
2458 This is the ``ASTImporterLookupTable`` class. This lookup table should be
2880 information provided by the table definition of the attribute. Ultimately, the
2910 This tablegen definition must derive from the ``Attr`` (tablegen, not
2926 arguments the attribute expects, and more. Most members of the ``Attr`` tablegen
2943                       syntax and placement.
2944   ``CXX11``           Spelled with a C++-style ``[[attr]]`` syntax with an
2946   ``C23``             Spelled with a C-style ``[[attr]]`` syntax with an
2949                       syntax.
2954                       ``[[attr]]`` syntax can be used, and appertains to
3025 Documentation is table generated on the public web server by a server-side
3036 Documentation derives from the ``Documentation`` tablegen type. All derived
3052 using reStructuredText (RST) syntax.
3114 not table generated nodes, new language options must be created manually and
3376      as syntax highlighting, cross-referencing, and so on.  The
3471 actual file itself. This can be done using the following syntax:
3496 The simple syntax above allows each specification to match exactly one
3497 diagnostic. You can use the extended syntax to customize this. The extended
3498 syntax is ``expected-<type> <n> {{diag text}}``, where ``<type>`` is one of
3537 The default matching mode is simple string, which looks for the expected text
3540 single newline character. This mode matches the emitted diagnostic when the
3544 string-mode parser accepts opening delimiters of more than two curly braces,
3556 Regex matching mode may be selected by appending ``-re`` to the diagnostic type