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

1 2 3 4 5 6 7 8 91011>>

  /src/share/doc/psd/20.ipctut/
pipe.c 34 #define DATA "Bright star, would I were steadfast as thou art . . ."
  /src/usr.bin/make/unit-tests/
opt-define.mk 14 # would not be possible if the variable had been specified on the command line
22 # "Internal" or in the "Command" scope instead, undefining it would have no
cond-token-number.mk 11 # Even though -0 is a number and would be accepted by strtod, it is not
22 # Even though +0 is a number and would be accepted by strtod, it is not
33 # Even though -1 is a number and would be accepted by strtod, it is not
44 # Even though +1 is a number and would be accepted by strtod, it is not
directive-for-empty.mk 30 # variables were real variables, calling 'empty' would work on them as well.
51 # loop would be naive and require many special cases, as there are many cases
109 # would be difficult to understand for humans as well. Technically, they are
112 # removed from the scope, which would need to make the outer 'i' visible
113 # again. This would suggest to use one variable scope per .for loop.
116 # a custom scope to be passed as parameter. This would have another side
119 # This would mean that the combination of a .for variable and the modifiers
120 # '::=', '::+=', '::?=', '::!=' and ':_' would lead to different behavior than
posix-varassign.mk 8 # as they would introduce the distinction between eagerly and lazily evaluated
10 # this would add too much complexity to the user's mental model, for too
recursive.mk 4 # This would stop make from doing anything since the "recursive" error
35 # brace would be detected directly in the line where it is produced.
varmod-order-numeric.mk 14 # To get 53-bit integers even in C90, it would be possible to switch to
15 # 'double' instead, but that would allow floating-point numbers as well, which
varparse-undef-partial.mk 39 # variable name, as would be expected from reading the expression.
56 # expression ${COMPILER} would be expanded several times, but in this simple
57 # scenario there would not be any side effects.
export.mk 20 ${:U!}= exclamation # A direct != would try to run "exclamation"
var-op-assign.mk 14 # is discarded. Otherwise the value would start with a single tab.
27 # The '$' needs to be escaped with another '$', otherwise it would refer to
42 # This alone would not produce any side-effects, therefore the variable has
89 # In safe mode, parsing would stop immediately after the "VARIABLE NAME="
varmod-loop-varname.mk 25 # The expression ${\:\:\:} would not work since backslashes can only
115 # loop variable to the value it had before the loop. This would result in
123 # would be neither defined nor nonempty since all expressions of the form
124 # ${var} would have been replaced with ${:Uword} before evaluating them.
varname-dollar.mk 7 # and $$ would always expand to the same value.
  /src/external/gpl3/gdb.old/dist/gdb/testsuite/lib/
compiler.F90 54 would define its version as e.g. 19.0.0 or rather __INTEL_COMPILER would be
  /src/external/gpl3/gdb/dist/gdb/testsuite/lib/
compiler.F90 54 would define its version as e.g. 19.0.0 or rather __INTEL_COMPILER would be
  /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
  /src/external/bsd/tre/dist/tests/agrep/
basic.ok 84 I suppose for something like that one would use a very large number of microphones.
94 I suppose for something like that one would use a very large number of microphones.
112 basic.in:I suppose for something like that one would use a very large number of microphones.
122 (standard input):I suppose for something like that one would use a very large number of microphones.
140 4:I suppose for something like that one would use a very large number of microphones.
150 4:I suppose for something like that one would use a very large number of microphones.
160 0:I suppose for something like that one would use a very large number of microphones.
170 0:I suppose for something like that one would use a very large number of microphones.
180 I suppose for something like that one would use a very large number of microphones.
190 I suppose for something like that one would use a very large number of microphones
    [all...]
  /src/external/gpl3/gcc/dist/contrib/
test_recheck 20 -n dry run, only show what would be run
  /src/external/gpl3/gcc.old/dist/contrib/
test_recheck 20 -n dry run, only show what would be run
  /src/external/lgpl3/gmp/dist/mpn/powerpc32/
mod_34lsub1.asm 50 C Fetching half words would allow add instead for accumulating, instead of
51 C adde and its serialization. An outer loop would be required though, since
52 C 2^16 halfwords can overflow. lhz+add would be 2.0 c/l, but if there's
54 C then the total would be 2.67 c/l which isn't much faster than the current
  /src/sys/arch/m68k/060sp/dist/
changes 105 stated that ONLY "bit 0" would be set. The 060SP attempts to set a few
127 stated that ONLY "bit 0" would be set. The 060SP attempts to set a few

Completed in 42 milliseconds

1 2 3 4 5 6 7 8 91011>>