Home
last modified time | relevance | path

Searched refs:blow (Results 1 – 25 of 74) sorted by relevance

123

/external/toybox/lib/
Ddeflate.c83 int click = bb->bitpos >> 3, blow, blen; in bitbuf_get() local
89 blow = bb->bitpos & 7; in bitbuf_get()
90 blen = 8-blow; in bitbuf_get()
92 result |= ((bb->buf[click] >> blow) & ((1<<blen)-1)) << offset; in bitbuf_get()
113 int click = bb->bitpos >> 3, blow, blen; in bitbuf_put() local
120 blow = bb->bitpos & 7; in bitbuf_put()
121 blen = 8-blow; in bitbuf_put()
123 bb->buf[click] |= data << blow; in bitbuf_put()
/external/rust/crates/regex/
DPERFORMANCE.md239 ## Excessive counting can lead to exponential state blow up in the DFA
241 **Advice**: Don't write regexes that cause DFA state blow up if you care about
246 an exponential blow up in the number of states. This crate specifically guards
247 against exponential blow up by doing two things:
262 In effect, this crate will detect exponential state blow up and fall back to
DHACKING.md53 are susceptible to exponential state blow up (where the worst case is computing
/external/llvm-project/llvm/test/Transforms/InstSimplify/ConstProp/
Dvscale-shufflevector.ll6 ; This test checks that SimplifyInstruction does not blow up in the face of
/external/e2fsprogs/doc/RelNotes/
Dv1.25.txt29 Fix problem which caused compile_et and mk_cmds to blow up if
/external/libchrome/mojo/public/interfaces/bindings/tests/
Dvalidation_test_interfaces.mojom132 // This is used to test that deeply recursive structures don't blow the stack.
/external/mesa3d/src/gallium/auxiliary/postprocess/
DADDING78 Testing, praying, hookers, blow, sacrificial lambs...
/external/llvm-project/llvm/test/DebugInfo/Generic/
Dtwo-cus-from-same-file.ll3 ; blow llc up and produces something reasonable.
/external/crosvm/ci/crosvm_base/
DDockerfile9 # of outdated libraries. Sid could blow up on us any day.
/external/llvm/test/DebugInfo/Generic/
Dtwo-cus-from-same-file.ll3 ; blow llc up and produces something reasonable.
/external/llvm/test/CodeGen/Thumb2/
Daligned-spill.ll35 ; and would probably blow MFI's mind.
/external/llvm-project/llvm/test/CodeGen/Thumb2/
Daligned-spill.ll35 ; and would probably blow MFI's mind.
/external/protobuf/objectivec/Tests/
DGPBArrayTests.m213 //% // Wrong type doesn't blow up.
557 // Wrong type doesn't blow up.
901 // Wrong type doesn't blow up.
1245 // Wrong type doesn't blow up.
1589 // Wrong type doesn't blow up.
1933 // Wrong type doesn't blow up.
2277 // Wrong type doesn't blow up.
2621 // Wrong type doesn't blow up.
2965 // Wrong type doesn't blow up.
/external/arm-trusted-firmware/docs/plat/
Dwarp7.rst151 The image_sign.sh and bl2_sign.csf files alluded to blow are available here.
/external/llvm-project/clang/lib/StaticAnalyzer/
DREADME.txt46 path-sensitivity. We reduce exponential blow-up by caching nodes. If
/external/clang/lib/StaticAnalyzer/
DREADME.txt46 path-sensitivity. We reduce exponential blow-up by caching nodes. If
/external/icu/icu4c/source/samples/ufortune/resources/
Droot.txt117 "A bird in the hand makes it awfully hard to blow your nose.",
/external/python/cpython2/Doc/howto/
Dlogging-cookbook.rst238 logger1.debug('Quick zephyrs blow, vexing daft Jim.')
253 10-22 22:19 myapp.area1 DEBUG Quick zephyrs blow, vexing daft Jim.
349 logger1.debug('Quick zephyrs blow, vexing daft Jim.')
447 59 myapp.area1 DEBUG Quick zephyrs blow, vexing daft Jim.
/external/python/cpython2/Misc/
DSpecialBuilds.txt186 objects can go away. COUNT_ALLOCS can blow up in 2.2 and 2.2.1 because of this;
/external/rust/crates/regex-automata/
DREADME.md218 seems to provide a way to character state blow up such that it is detectable.
/external/llvm-project/llvm/test/CodeGen/AArch64/GlobalISel/
Dswifterror.ll304 ; Check that we don't blow up on tail calling swifterror argument functions.
/external/google-breakpad/src/client/mac/sender/
Dcrash_report_sender.m113 // sizeToFit will blow out the width rather than making the field taller, so
/external/llvm-project/llvm/docs/
DLibFuzzer.rst537 two similar inputs as significantly different and it will blow up the test corpus.
700 is enabled, it will also instrument the LLVM support code which will blow up the
/external/llvm/docs/
DLibFuzzer.rst610 two similar inputs as significantly different and it will blow up the test corpus.
809 is enabled, it will also instrument the LLVM support code which will blow up the
/external/llvm-project/llvm/test/CodeGen/ARM/
Dswifterror.ll380 ; Check that we don't blow up on tail calling swifterror argument functions.

123