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

1 2 3 4

  /src/usr.bin/make/unit-tests/
opt-warnings-as-errors.exp 2 make: parsing warnings being treated as errors
4 parsing continues
directive-for-null.mk 3 # Test for parsing a .for loop that accidentally contains a null byte.
opt-warnings-as-errors.mk 6 # First, the word "warning" is still printed, and second, parsing continues
17 _!= echo 'parsing continues' 1>&2
lint.mk 8 # then, make checked for parse errors only after parsing each top-level
12 # Ouch: as of 2020-08-03, the variable is malformed and parsing stops
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
dep-op-missing.mk 8 # but that is removed in an early stage of parsing.
error.mk 4 # continuing parsing until the end of the file.
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...]
gnode-submake.mk 9 # from parsing is available in compat mode as well.
opt-debug-for.mk 4 # parsing and evaluating .for loops.
opt-no-action.mk 11 != echo 'command during parsing' 1>&2; echo
opt-query.exp 2 command during parsing
opt.mk 14 # Just to see how the custom argument parsing code reacts to a syntax
dep.mk 20 # the first ';', without parsing expressions as such. It interpreted the
opt-debug-parse.mk 4 # makefile parsing.
cond-cmp-numeric-ne.mk 40 # Numeric comparison works by parsing both sides
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}:"
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.
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/
sanitizer_flag_parser.cc 101 if (!res) fatal_error("Flag parsing failed.");

Completed in 18 milliseconds

1 2 3 4