Home
last modified time | relevance | path

Searched full:encounter (Results 1 – 25 of 342) sorted by relevance

12345678910>>...14

/freebsd/usr.bin/find/
H A Doperator.c170 * if we encounter a ( expression ) then look for nots in in not_squish()
177 * if we encounter a not, then snag the next node and place in not_squish()
194 * If we encounter ! ( expr ) then look for nots in in not_squish()
232 * if we encounter a ( expression ) then look for or's in in or_squish()
238 /* if we encounter a not then look for or's in the subplan */ in or_squish()
243 * if we encounter an or, then place our collected plan in the in or_squish()
/freebsd/sys/contrib/dev/ice/
H A DREADME164 If you encounter issues with the DDP package file, you may need to
/freebsd/sys/contrib/device-tree/Bindings/net/wireless/
H A Dsilabs,wfx.yaml26 it, you may encounter issues during reboot. The mmc-pwrseq should be
57 during probe. Without this property, you may encounter issues with warm
/freebsd/sys/contrib/device-tree/Bindings/staging/net/wireless/
H A Dsilabs,wfx.yaml27 it, you may encounter issues during reboot. The mmc-pwrseq should be
65 during probe. Without this property, you may encounter issues with warm
/freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Checkers/WebKit/
H A DASTUtils.h43 /// subexpressions to get to the relevant child nodes. Whenever we encounter a
48 /// If \p StopAtFirstRefCountedObj is true and we encounter a subexpression that
/freebsd/contrib/llvm-project/llvm/lib/CodeGen/SelectionDAG/
H A DStatepointLowering.h63 /// Record the fact that we expect to encounter a given gc_relocate
85 // TODO: Should add consistency tracking to ensure we encounter
/freebsd/contrib/llvm-project/compiler-rt/include/xray/
H A Dxray_interface.h113 /// id. We return 0 if we encounter any error, even if 0 may be a valid function
118 /// encounter errors (when there are no instrumented functions, etc.).
/freebsd/contrib/sendmail/doc/op/
H A DREADME3 If you encounter the error:
/freebsd/usr.bin/diff/
H A Dxmalloc.h10 * failure (they call fatal if they encounter an error).
H A Dxmalloc.c7 * failure (they call fatal if they encounter an error).
/freebsd/crypto/openssh/
H A Dxmalloc.h10 * failure (they call fatal if they encounter an error).
H A Dxmalloc.c7 * failure (they call fatal if they encounter an error).
/freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/Scalar/
H A DLoopSimplifyCFG.h11 // encounter a noncanonical CFG construct that causes another loop pass to
/freebsd/contrib/llvm-project/compiler-rt/lib/xray/
H A Dxray_interface.cpp63 // This is the function to call when we encounter the entry or exit sleds.
69 // This is the function to call when we encounter a custom event log call.
72 // This is the function to call when we encounter a typed event log call.
/freebsd/contrib/bmake/
H A DREADME51 If you encounter a system that bmake does not build or work on *out of
/freebsd/crypto/openssl/doc/man3/
H A DBN_copy.pod24 these restrictions may encounter unexpected side effects or crashes. For that
/freebsd/contrib/llvm-project/clang/include/clang/AST/
H A DMangleNumberingContext.h30 // The index of the next lambda we encounter in this context.
/freebsd/contrib/bzip2/
H A DREADME.COMPILATION.PROBLEMS24 you'll encounter are not Large Files.
/freebsd/usr.sbin/bsdconfig/include/
H A Dusage.hlp8 encounter during this installation:
/freebsd/contrib/llvm-project/llvm/lib/XRay/
H A DFDRRecords.cpp10 // of records we encounter in XRay flight data recorder mode traces.
/freebsd/share/doc/psd/21.ipc/
H A D1.t99 which sophisticated users are likely to encounter when using
/freebsd/contrib/llvm-project/llvm/include/llvm/DebugInfo/CodeView/
H A DStringsAndChecksums.h51 // While in practice we should never encounter a string table even in initialize()
/freebsd/lib/msun/src/
H A Ds_nan.c41 * encounter an invalid character, NUL, etc. If we overflow, we do
/freebsd/sys/contrib/dev/athk/ath10k/
H A Dcoredump.h128 * we may encounter error in the dump processing.
/freebsd/contrib/netbsd-tests/lib/libpthread/
H A Dt_fpu.c45 * any problems you encounter but we cannot promise a timely correction."

12345678910>>...14