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

1 2

  /src/tests/usr.bin/xlint/lint1/
lex_char.c 82 * occur in practice though.
  /src/usr.bin/make/unit-tests/
opt-debug-curdir.mk 4 # as the string "DEBUG(CWD" does not occur in the source code.
check-expect.lua 12 Each <line> must occur in the .exp file.
16 Each <message> must occur in the .exp file and refer back to the
27 The <substring> must not occur as part of any line in the .exp file.
31 must not occur as part of any line in the .exp file.
cond-eof.mk 13 # These syntax errors are an edge case that does not occur during normal
var-recursive.mk 30 # follow-up error messages, but recursive variables occur seldom.
opt-jobs.mk 38 EXPECT..5e1C= <integer> # unlikely to occur in practice
directive-for-empty.mk 68 # can occur in a string literal as well.
74 # Conditions, including function calls to 'empty', can not only occur in
75 # condition directives, they can also occur in the modifier ':?', see
varname-empty.mk 56 # could be several lines away or not occur at all. While looking for the
var-op-default.mk 65 # places where expressions can occur. If in doubt, enable the
var-op-sunsh.mk 87 # The ':sh' is the only word that may occur between the variable name and
96 # The word ':sh' is not the only thing that can occur after a variable name.
deptgt-makeflags.mk 109 # Unbalanced quotes produce an error message. If they occur anywhere in the
parse-var.mk 80 # side of the assignment, but only if they occur inside expressions.
var-eval-short.mk 21 # TODO: Test the modifiers in the same order as they occur in ApplyModifier.
varmod-loop-varname.mk 24 # ":::" is a very creative variable name, unlikely to occur in practice.
cond-op.mk 30 # This kind of condition looks so unfamiliar that it doesn't occur in
cond-token-var.mk 120 # but undefined variables may occur in the variable name or in modifiers.
cond-token-plain.mk 100 # A bare word may occur alone in a condition, without any comparison
262 # evaluated twice. In practice, expressions that occur in conditions do not
cond-short.mk 187 # to occur in expressions. In this mode, the variable name 'VAR' was
Makefile 538 ${:D The following lines should rather not occur since the job } \
  /src/sys/arch/m68k/060sp/dist/
isp.doc 189 data registers, and BEFORE the actual emulated transfers occur, the
isp.s 394 # If none of these occur, then a normal exit is made through #
510 btst &idbyz_bit,SPCOND_FLG(%a6) # did divide-by-zero occur?
522 btst &idbyz_bit,SPCOND_FLG(%a6) # did divide-by-zero occur?
2253 # the first two quotient words must be zero, or overflow would occur.
3050 tst.l %d0 # did error occur?
3298 # pre-load the operand ATC. no page faults should occur here because
3600 # pre-load the operand ATC. no page faults should occur because
3909 # pre-load the operand ATC. no page faults should occur here because
4067 # pre-load the operand ATC. no page faults should occur here because
4213 # pre-load the operand ATC. no page faults should occur here becaus
    [all...]
pfpsp.s 1165 # emulated and exceptions handled. The differences occur in how the #
1172 # performed by calling the routine fout(). If no exception should occur #
1176 # should occur, then we must create an exception stack frame of that #
1399 btst &unfl_bit,FPSR_EXCEPT(%a6) # did disabled underflow occur?
1401 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did disabled overflow occur?
1977 btst &unfl_bit,FPSR_EXCEPT(%a6) # did disabled underflow occur?
1979 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did disabled overflow occur?
2662 # no exception occurred. now, did a disabled, exact overflow occur with inexact
2664 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did overflow occur?
2682 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did overflow occur
    [all...]
fpsp.s 1165 # emulated and exceptions handled. The differences occur in how the #
1172 # performed by calling the routine fout(). If no exception should occur #
1176 # should occur, then we must create an exception stack frame of that #
1399 btst &unfl_bit,FPSR_EXCEPT(%a6) # did disabled underflow occur?
1401 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did disabled overflow occur?
1977 btst &unfl_bit,FPSR_EXCEPT(%a6) # did disabled underflow occur?
1979 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did disabled overflow occur?
2662 # no exception occurred. now, did a disabled, exact overflow occur with inexact
2664 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did overflow occur?
2682 btst &ovfl_bit,FPSR_EXCEPT(%a6) # did overflow occur
    [all...]
ilsp.s 303 # the first two quotient words must be zero, or overflow would occur.
  /src/sys/external/bsd/compiler_rt/dist/lib/asan/tests/
asan_mac_test_helpers.mm 62 access_memory(&kStartupStr[i]); // make sure no optimizations occur.

Completed in 26 milliseconds

1 2