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

1 2 3 4 5 6 7 8 9

  /src/share/doc/psd/20.ipctut/
pipe.c 34 #define DATA "Bright star, would I were steadfast as thou art . . ."
  /src/external/gpl3/gdb/dist/sim/testsuite/h8300/
movmd.s 57 # Now make sure exactly 10 bytes were transferred.
88 # Now make sure exactly 20 bytes were transferred.
119 # Now make sure exactly 40 bytes were transferred.
movsd.s 47 # Now make sure exactly 4 bytes were transferred.
84 # Now make sure 5 bytes were transferred, and the 6th is zero.
  /src/external/gpl3/gdb.old/dist/sim/testsuite/h8300/
movmd.s 57 # Now make sure exactly 10 bytes were transferred.
88 # Now make sure exactly 20 bytes were transferred.
119 # Now make sure exactly 40 bytes were transferred.
movsd.s 47 # Now make sure exactly 4 bytes were transferred.
84 # Now make sure 5 bytes were transferred, and the 6th is zero.
  /src/usr.bin/make/unit-tests/
directive-unexport-env.mk 9 # were not properly detected.
varmod-to-abs.mk 10 # variable with the same name as the path that is to be resolved. There were
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.
cond-late.mk 33 # If the order of evaluation were to change to first parse the condition
dep-colon-bug-cross-file.mk 24 # for this is that in MainParseArgs, the command line arguments were not
deptgt-end-jobs.mk 45 # Instead, the deferred commands of the .END node are run as if they were
deptgt-end.mk 44 # Instead, the deferred commands of the .END node are run as if they were
varmod-order-numeric.mk 7 # The variable modifiers ':On', ':Onr' and ':Orn' were added in var.c 1.939
varname-dot-parsedir.mk 12 # .PARSEDIR and .PARSEFILE were added on 1999-08-09.
varname-dot-parsefile.mk 12 # .PARSEDIR and .PARSEFILE were added on 1999-08-09.
cond-short.mk 13 # parse them. They were still evaluated though, the only difference to
15 # expressions, undefined variables were allowed. This allowed for conditions
160 # the comparison were still parsed and evaluated. Comparing these two values
185 # side of the '&&' irrelevant. Back then, irrelevant condition parts were
203 # The manual page stated from at least 1993 on that irrelevant conditions were
204 # not evaluated, but that was wrong. These conditions were evaluated, the
varmod-ifelse.mk 19 # word "expression". If the name were expanded lazily, everything would be
211 # At 2020-01-01, the expressions from the 'then' and 'else' branches were
214 # the '}}' were ordinary characters. When the branch was not taken, the
258 # parsed in balanced mode, ignoring that the inner '}}' were ordinary
259 # characters. The '}}' were thus interpreted as the end of the 'else' branch
301 # were parsed differently, depending on whether the branch was active or not.
cond-op.mk 14 # If || were to bind more tightly than &&, the result would be different
20 # If make were to interpret the && and || operators like the shell, the
  /src/external/gpl3/binutils/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were
  /src/external/gpl3/binutils.old/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were
  /src/external/gpl3/gcc/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were
  /src/external/gpl3/gcc.old/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were
  /src/external/gpl3/gdb/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were
  /src/external/gpl3/gdb.old/dist/config/
bootstrap-debug-lib.mk 2 # stage3 would have generated the same executable code if they were

Completed in 18 milliseconds

1 2 3 4 5 6 7 8 9