HomeSort by: relevance | last modified time | path
    Searched refs:parsing (Results 1 - 25 of 59) sorted by relevancy

1 2 3

  /src/usr.bin/make/unit-tests/
opt-warnings-as-errors.exp 2 make: parsing warnings being treated as errors
4 parsing continues
var-op-expand.exp 10 while parsing "${:Z1}:${:Z2}}"
13 while parsing "${:Z2}}"
opt-no-action.exp 1 command during parsing
varname-dot-makeflags.mk 28 # when parsing the makefiles. This is different from exported variables,
34 # After parsing, the environment variable 'MAKEFLAGS' is set based on the
parse-var.mk 3 # Tests for parsing expressions.
45 # for the long forms, EOF after parsing a modifier
70 # How much does the parsing position advance (pp)?
89 # 2023-02-18, the exact way of parsing an expression with subexpressions
92 # If it was evaluated, nested expressions were parsed correctly, parsing each
122 # contains more '{' than '}', parsing failed with the error message 'Unfinished
varmod-ifelse.exp 57 while parsing "${:X-else}}"
62 while parsing "${:Z1}:${:Z2}}>"
65 while parsing "${:Z2}}>"
varmod-ifelse.mk 138 # When parsing such an expression, the parser used to be strict. It first
139 # evaluated the left-hand side of the operator '&&' and then started parsing
145 # therefore parsing stopped at the '>', producing the 'Bad conditional
148 # Ideally, the conditional expression would not be expanded before parsing
202 # When parsing the modifier ':?', there are 3 possible cases:
218 # In var.c 1.285 from 2020-07-20, the parsing of the expressions changed so
225 # reverted, still not knowing about the difference between regular parsing and
226 # balanced-mode parsing.
229 # inconsistency in parsing, but since that broke parsing of the modifier ':@'
    [all...]
cond-eof.mk 3 # Tests for parsing the end of '.if' conditions, which are represented as the
deptgt.exp 3 Parsing deptgt.mk:36: ${:U}: empty-source
5 Parsing deptgt.mk:37: : command for empty targets list
6 Parsing deptgt.mk:38: : empty-source
8 Parsing deptgt.mk:39: : command for empty targets list
9 Parsing deptgt.mk:40: .MAKEFLAGS: -d0
20 while parsing "${:U:Z}:"
opt-query.exp 2 command during parsing
var-op-assign.mk 24 # early stage of parsing and applies to all line types, except for the
67 # the implementation of the parser, which cheats when parsing a variable
68 # name. It only counts parentheses and braces instead of properly parsing
89 # In safe mode, parsing would stop immediately after the "VARIABLE NAME="
94 # expect+1: Parsing still continues until here.
95 .info Parsing still continues until here.
cmdline.mk 3 # Tests for command line parsing and related special variables.
44 # low-level parsing from ParseRawLine does not take place.
deptgt-makeflags.mk 7 # during parsing.
44 # When parsing this line, each '$$' becomes '$', resulting in '$$$$'.
70 # parsing. The ':=' assignment operator expands the empty
varmod-defined.mk 60 # Instead, the :D modifier is implemented sanely by parsing nested
90 # TODO: Add more tests for parsing the plain text part, to cover each branch
109 # out-of-bounds read when parsing the indirect ':U' modifier.
cond-cmp-numeric-eq.mk 43 # Numeric comparison works by parsing both sides
cond-late.mk 6 # Any expressions appearing in these conditions are expanded before parsing
recursive.mk 30 # can be achieved by just parsing the variable and not evaluating it.
var-eval-short.exp 2 while parsing "${:Uword:@${FAIL}@expr@}"
3 Parsing var-eval-short.mk:158: .if 0 && ${0:?${FAIL}then:${FAIL}else}
6 Parsing modifier ${0:?...}
12 Parsing var-eval-short.mk:166: DEFINED= defined
14 Parsing var-eval-short.mk:167: .if 0 && ${DEFINED:L:?${FAIL}then:${FAIL}else}
17 Parsing modifier ${DEFINED:L}
19 Parsing modifier ${DEFINED:?...}
25 Parsing var-eval-short.mk:169: .MAKEFLAGS: -d0
var-recursive.mk 38 # which takes a different code path in Var_Parse for parsing the variable
varmod.mk 8 # As of 2024-06-05, the possible behaviors during parsing are:
10 # * `strict`: the parsing style used by most modifiers:
17 # * `no-colon`: after parsing this modifier, the following modifier
21 # * `individual`: parsing this modifier does not follow the common
varname-dot-parsedir.mk 20 # During parsing, it is possible to undefine .PARSEDIR.
varname-dot-parsefile.mk 18 # During parsing, it is possible to undefine .PARSEFILE.
cond-token-plain.mk 14 # condition since comment parsing is done in an early phase and removes the
33 # in a very early parsing phase.
227 # looks suspicious of evaluating the expression twice: first for parsing a
228 # bare word and second for parsing the left-hand side of a comparison.
247 # 2021-12-30, the condition in such an expression is evaluated before parsing
  /src/bin/sh/
parser.h 170 extern int parsing;
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/
sanitizer_flag_parser.cc 101 if (!res) fatal_error("Flag parsing failed.");

Completed in 36 milliseconds

1 2 3