Home
last modified time | relevance | path

Searched refs:destructive (Results 1 – 25 of 44) sorted by relevance

12

/external/ltp/testcases/kernel/fs/scsi/ltpfs/
Dltpfsio.sh33 …- These operations are destructive so do NOT point the tests to partitions where the data shouldn'…
/external/ltp/testcases/kernel/fs/scsi/ltpscsi/
Dltpfsscsi.sh31 …- These operations are destructive so do NOT point the tests to partitions where the data shouldn'…
/external/ltp/testscripts/
Dltpfsnolvm.sh40 …- These operations are destructive so do NOT point the tests to partitions where the data shouldn'…
Dltpfslvm.sh43 …- These operations are destructive so do NOT point the tests to partitions where the data shouldn'…
Dltp-aiodio.sh55 …- WARNING !! The partition you pass will be overwritten. This is a destructive test so only pass a…
/external/autotest/server/site_tests/power_DeferForFlashrom/
Dcontrol13 potentially-destructive write operations and that powerd defers suspend or
/external/fio/examples/
Dssd-steadystate.fio14 # It's not destructive in the sense that it will ruin the device, but
/external/antlr/antlr-3.4/runtime/ObjC/Framework/
DFastQueue.m83 /** Return string of current buffer contents; non-destructive */
DANTLRCommonTreeNodeStream.m228 /** For debugging; destructive: moves tree iterator to end. */
/external/ltp/testcases/kernel/io/disktest/
DREADME129 - non-destructive read/write IO function
/external/swiftshader/third_party/LLVM/docs/HistoricalNotes/
D2001-05-18-ExceptionHandling.txt198 nondestructive walk that builds a stack trace, then a destructive walk that
/external/llvm/docs/HistoricalNotes/
D2001-05-18-ExceptionHandling.txt198 nondestructive walk that builds a stack trace, then a destructive walk that
/external/llvm/docs/
DStackMaps.rst141 be overwritten by destructive patching. Without shadow bytes, this
142 destructive patching could overwrite program text or data outside the
/external/eigen/doc/
DTutorialMatrixClass.dox161 …no-operation if the actual matrix size doesn't change; otherwise it is destructive: the values of …
/external/libvpx/libvpx/third_party/x86inc/
Dx86inc.asm1292 ;%4 == 1 if non-destructive or 4-operand (xmm, xmm, xmm, imm), 0 otherwise
/external/llvm/lib/Target/X86/
DREADME-SSE.txt197 This looks really bad. The problem is shufps is a destructive opcode. Since it
DX86InstrShiftRotate.td902 // Prefer RORX which is non-destructive and doesn't update EFLAGS.
/external/swiftshader/third_party/LLVM/lib/Target/X86/
DREADME-SSE.txt227 This looks really bad. The problem is shufps is a destructive opcode. Since it
/external/vixl/test/aarch64/
Dtest-simulator-aarch64.cc1526 bool destructive = (vd_bits == kBRegSize) || (vd_bits == kSRegSize); in Test1OpAcrossNEON_Helper() local
1562 if (destructive) { in Test1OpAcrossNEON_Helper()
/external/gptfdisk/
DNEWS984 - Added non-destructive write test when opening the device file, in order
/external/e2fsprogs/po/
De2fsprogs.pot3616 msgid "Checking for bad blocks in non-destructive read-write mode\n"
3620 msgid "Checking for bad blocks (non-destructive read-write test)\n"
Dsr.po3964 msgid "Checking for bad blocks in non-destructive read-write mode\n"
3969 msgid "Checking for bad blocks (non-destructive read-write test)\n"
Dzh_CN.po3781 msgid "Checking for bad blocks in non-destructive read-write mode\n"
3785 msgid "Checking for bad blocks (non-destructive read-write test)\n"
Duk.po3974 msgid "Checking for bad blocks in non-destructive read-write mode\n"
3978 msgid "Checking for bad blocks (non-destructive read-write test)\n"
/external/bison/data/m4sugar/
Dm4sugar.m41356 # destructive, this macro is generally used twice, with a temporary

12