HomeSort by: relevance | last modified time | path
    Searched refs:probably (Results 1 - 24 of 24) sorted by relevancy

  /src/sys/external/isc/libsodium/dist/test/default/
kdf.exp 11 Failure -- probably expected for output length=0
12 Failure -- probably expected for output length=1
13 Failure -- probably expected for output length=2
14 Failure -- probably expected for output length=3
15 Failure -- probably expected for output length=4
16 Failure -- probably expected for output length=5
17 Failure -- probably expected for output length=6
18 Failure -- probably expected for output length=7
19 Failure -- probably expected for output length=8
20 Failure -- probably expected for output length=
    [all...]
  /src/usr.bin/make/unit-tests/
cmdline-redirect-stdin.mk 22 # probably buffers its input. Most shells use unbuffered stdin, and this
directive-if.exp 9 make: directive-if.mk:66: Quotes in plain words are probably a mistake.
dep-var.mk 5 # Uh oh, this feels so strange that probably nobody uses it. But it seems to
50 # therefore this feature is probably not widely used.
64 # probably be appropriate to just error out in such a case.
cmdline-undefined.mk 8 # (which probably occurs rarely in practice, if at all), but their
cond-late.mk 12 # should not contain double-quotes, or the parser will probably fail.
recursive.mk 24 # Seen in pkgsrc/x11/libXfixes, and probably many more package that use
cond-undef-lint.mk 30 # The variable name depends on the undefined variable, which is probably a
archive.mk 18 # dir.c would probably not handle this correctly, therefore each of the
var-op-assign.mk 90 # line, since any commands run after that are probably working with
var-scope-cmdline.mk 55 # temporary loop variable after finishing the loop. It was probably not
varparse-errors.mk 55 # misleading anyway, that piece of code is probably not necessary. The wrong
varmod-sysv.mk 98 # This was probably a copy-and-paste mistake since the code for the SysV
varmod-to-separator.mk 118 # probably been an oversight during implementation. For consistency, the
  /src/distrib/mvme68k/miniroot/
install.md 154 It's probably also wisest not to touch the '8 partitions:' line, even
183 and rational way. You'll be asked several questions, and it would probably be
  /src/usr.sbin/sysinst/arch/i386/
msg.md.en 117 probably 1023, 255 and 63 - this is correct).
  /src/usr.sbin/sysinst/arch/mac68k/
msg.md.en 129 is probably because your disk formatter didn't reserve additional space
  /src/share/mk/
bsd.x11.mk 382 echo "pkg-config ${.TARGET} matches @.*@, probably missing updates" 1>&2; \
494 echo "manual ${.TARGET} matches @.*@, probably missing updates" 1>&2; \
  /src/sys/arch/m68k/m68k/
copy.s 109 * This is probably not the best we can do, but it is still 2-10 times
170 * This is probably not the best we can do, but it is still 2-10 times
  /src/sys/arch/x68k/stand/boot_ufs/
boot.S 186 | ROM boot ... probably from SCSI
221 | no information in d2 -- probably from BOOT MENU
  /src/bin/csh/
func.c 1362 * probably a background eval, e.g. "eval date &", and we want to
  /src/distrib/sets/
fmt-list 262 -- of 8. There are probably reasons for the large indentation.
  /src/distrib/syspkg/mk/
bsd.syspkg.mk 417 # You probably won't need to touch these
432 # Will probably not work with PACKAGE_DEPENDS_WITH_PATTERNS=false ...
  /src/sys/arch/sparc64/sparc64/
locore.s 1980 bne,pt %icc, winfixfill ! our stack's probably bad so we need to switch somewhere else
1993 wrpr %g0, 7, %cansave ! probably is too, so blow away
2296 * probably (if we were doing a flushw then we may have
3660 bne,pt %icc, checkalignspill ! our stack's probably bad so we need to switch somewhere else
3673 wrpr %g0, 7, %cansave ! probably is too, so blow away
6464 and %o2, %o1, %o1 ! (probably not necessary)

Completed in 314 milliseconds