| /src/usr.bin/make/unit-tests/ |
| cond-late.mk | 3 # Using the :? modifier, expressions can contain conditional
4 # expressions that are evaluated late, at expansion time.
6 # Any expressions appearing in these conditions are expanded before parsing
8 # expressions are evaluated individually and only as far as necessary, see
|
| unexport.mk | 13 # been replaced with a simple space, and expressions are not yet expanded.
|
| varmod-remember.mk | 55 # expressions into account. Due to this inconsistency that short expressions
56 # are possible but long expressions aren't, the name of the temporary variable
70 # the evaluation of the outer expression. If the expressions were evaluated
|
| varname-dot-make-save_dollars.mk | 21 # dollars, but also to those that come indirectly from other expressions.
33 # dollars, but also to those that come indirectly from other expressions.
63 # The '$' from the ':U' expressions do not appear as literal '$$' to the
93 # in indirect expressions.
|
| cond-token-plain.exp | 40 make: cond-token-plain.mk:139: Numbers can be composed from literals and expressions.
42 make: cond-token-plain.mk:144: Numbers can be composed from literals and expressions.
|
| var-op-default.mk | 49 # expressions in variable names, which made make much more versatile.
64 # in and around the code that expands expressions in the various
65 # places where expressions can occur. If in doubt, enable the
|
| cond-eof.mk | 14 # operation. Still, it is easy to avoid evaluating these expressions, just in
|
| directive-include.mk | 34 # The filename to be included can contain expressions.
38 # Expressions in double quotes or angle quotes are first parsed naively, to
39 # find the closing '"'. In a second step, the expressions are expanded. This
40 # means that the expressions cannot include the characters '"' or '>'. This
41 # restriction is not practically relevant since the expressions inside
|
| opt-debug-lint.mk | 4 # to catch common mistakes, such as unclosed expressions.
88 # expressions and unknown operators. During this check, the subexpression
94 # level of expressions. The unexpanded '$' then resulted in a wrong
98 # unclosed expressions and unknown modifiers is skipped.
|
| opt-debug-var.mk | 19 # The usual form of expressions is ${VAR}. The form $(VAR) is used
|
| varmod-defined.mk | 23 # be used in .if conditions. In this place, other undefined expressions
32 # The modifier text may contain plain text as well as expressions.
49 # Like in several other places in expressions, when
61 # expressions as such, without trying any shortcuts. See ParseModifier_Match
|
| varname-dollar.mk | 6 # If there really were a special variable named '$', the expressions ${${DOLLAR}}
|
| varname-make_print_var_on_error-jobs.mk | 7 # expressions expanded, just as they were printed to the shell command file.
|
| varparse-errors.mk | 3 # Tests for parsing and evaluating all kinds of expressions.
60 # be 2 expressions that create a parse error, which in this case is ':OX'.
61 # These expressions must be nested in some way. The below expressions are
|
| cond-token-plain.mk | 118 # Bare words may be intermixed with expressions.
138 # expect+1: Numbers can be composed from literals and expressions.
139 . info Numbers can be composed from literals and expressions.
143 # expect+1: Numbers can be composed from literals and expressions.
144 . info Numbers can be composed from literals and expressions.
246 # situation arises in expressions of the form ${cond:?yes:no}. As of
262 # evaluated twice. In practice, expressions that occur in conditions do not
|
| directive-export-gmake.mk | 75 # The 'export' directive expands expressions, but the expressions must not
76 # contain a ':', due to the overly strict parser. The indirect expressions
|
| parse-var.mk | 3 # Tests for parsing expressions.
80 # side of the assignment, but only if they occur inside expressions.
92 # If it was evaluated, nested expressions were parsed correctly, parsing each
|
| cmd-errors-jobs.mk | 3 # Demonstrate how errors in expressions affect whether the commands
25 # Undefined variables in expressions are not an error. They expand to empty
|
| cond-short.mk | 12 # possible to skip evaluation of irrelevant expressions and only
14 # relevant expressions was that in the irrelevant
15 # expressions, undefined variables were allowed. This allowed for conditions
187 # to occur in expressions. In this mode, the variable name 'VAR' was
199 # evaluated. In irrelevant expressions that are enclosed in double quotes,
200 # expressions based on undefined variables are allowed and evaluate to an
215 # evaluated as usual, resolving nested undefined expressions to an empty
263 # variables may be used in these expressions without generating an error.
|
| var-scope-local.mk | 73 # The target-local variables can be used in expressions, just like other
74 # variables. When these expressions are evaluated outside of a target, these
75 # expressions are not yet expanded, instead their text is preserved, to allow
76 # these expressions to expand right in time when the target-local variables
82 # see the command line option '-e'). In that phase, expressions involving
91 # expressions like ${@}, ${.TARGET} ${VAR:Mpattern} (see Var_Parse,
114 # text is used instead. This preserves the expressions based on target-local
119 # In the following examples, the expressions are based on target-local
|
| varmod-undefined.mk | 25 # The expressions in the text of the :U modifier may be arbitrarily
32 # The nested expressions may contain braces, and these braces don't
|
| cmdline-undefined.mk | 3 # Tests for undefined variables in expressions in the command line.
|
| cond-func-defined.mk | 46 # In .for loops, expressions based on the loop variables are substituted at
52 # Expressions in the argument of a function call don't have to be defined.
|
| /src/external/gpl3/gcc/dist/gcc/ |
| tree-ssa-pre.cc | 69 to move expressions further up than PRE would do, to make
82 2. Strength reduction can be performed by anticipating expressions
85 commutative expressions split up over multiple statements.
90 represent the actual statement containing the expressions we care about,
97 generation of values/expressions by a given block. We use them
104 expressions/values.
107 anticipatable expressions. ANTIC is a backwards dataflow
112 expressions, because the flow goes backwards through phis. We must
121 expressions fully redundant.
144 Fourth, we eliminate fully redundant expressions
323 static vec<pre_expr> expressions; variable
487 bitmap_head expressions; member in class:bitmap_set
[all...] |
| /src/external/gpl3/gcc.old/dist/gcc/ |
| tree-ssa-pre.cc | 69 to move expressions further up than PRE would do, to make
82 2. Strength reduction can be performed by anticipating expressions
85 commutative expressions split up over multiple statements.
90 represent the actual statement containing the expressions we care about,
97 generation of values/expressions by a given block. We use them
104 expressions/values.
107 anticipatable expressions. ANTIC is a backwards dataflow
112 expressions, because the flow goes backwards through phis. We must
121 expressions fully redundant.
144 Fourth, we eliminate fully redundant expressions
323 static vec<pre_expr> expressions; variable
499 bitmap_head expressions; member in class:bitmap_set
[all...] |
