Searched refs:speculative (Results 1 – 25 of 59) sorted by relevance
123
/external/ltp/testcases/open_posix_testsuite/scripts/ |
D | generate-makefiles.sh | 54 test_prefix=$(basename $(echo "$prereq_dir" | sed s/speculative//)) 161 @if [ -d speculative ]; then \$(MAKE) -C speculative all; fi 165 @if [ -d speculative ]; then \$(MAKE) -C speculative clean; fi 174 @if [ -d speculative ]; then \$(MAKE) -C speculative install; fi
|
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/NVPTX/ |
D | speculative-execution-divergent-target.ll | 1 ; Checks that speculative-execution only runs on divergent targets, if you pass 4 ; RUN: opt < %s -S -mtriple=nvptx-nvidia-cuda -speculative-execution | \ 6 ; RUN: opt < %s -S -mtriple=nvptx-nvidia-cuda -speculative-execution \ 9 ; RUN: opt < %s -S -speculative-execution -spec-exec-only-if-divergent-target | \
|
/external/llvm/test/CodeGen/NVPTX/ |
D | speculative-execution-divergent-target.ll | 1 ; Checks that speculative-execution only runs on divergent targets, if you pass 4 ; RUN: opt < %s -S -mtriple=nvptx-nvidia-cuda -speculative-execution | \ 6 ; RUN: opt < %s -S -mtriple=nvptx-nvidia-cuda -speculative-execution \ 9 ; RUN: opt < %s -S -speculative-execution -spec-exec-only-if-divergent-target | \
|
/external/arm-neon-tests/ |
D | InitCache.s | 33 ;ORR r0, r0, #(0x1 << 4) ;Enables speculative accesses on AXI 34 ORR r0, r0, #(0x1 << 4) ;Enables speculative accesses on AXI
|
/external/ltp/testcases/open_posix_testsuite/Documentation/ |
D | HOWTO_ConformanceTest | 63 to define are considered speculative by PTS and are created in a 64 speculative/ directory off of the functional area directory. (For 65 example, mq_timedsend/speculative.)
|
/external/ltp/testcases/open_posix_testsuite/ |
D | ChangeLog | 38 - pthread_cond_destroy/speculative/4-1.c, pthread_mutex_destroy/ 39 speculative/4-2.c, pthread_exit/3-1.c: 62 - pthread_rwlock_trylock/3-1.c: Moved to speculative. 80 pthread_mutex_init/speculative/5-2.c,
|
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/PGOProfile/ |
D | counter_promo_mexits.ll | 1 ; RUN: opt < %s -pgo-instr-gen -instrprof -do-counter-promotion=true -speculative-counter-promotion… 2 ; RUN: opt < %s --passes=pgo-instr-gen,instrprof -do-counter-promotion=true -speculative-counter-pr…
|
D | counter_promo_exit_merge.ll | 1 ; RUN: opt < %s -instrprof -do-counter-promotion=true -speculative-counter-promotion-max-exiting=3 … 2 ; RUN: opt < %s --passes=instrprof -do-counter-promotion=true -speculative-counter-promotion-max-ex…
|
/external/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_init/ |
D | coverage.txt | 10 speculative/5-2.c: Test for EPERM. Not available on
|
/external/ltp/testcases/open_posix_testsuite/conformance/interfaces/sched_rr_get_interval/ |
D | coverage.txt | 11 5 YES speculative test
|
/external/ltp/testcases/open_posix_testsuite/conformance/interfaces/sched_get_priority_min/ |
D | coverage.txt | 9 speculative for AIX (FIFO2, FIFO3, FIFO4)
|
/external/ltp/testcases/open_posix_testsuite/conformance/interfaces/sched_getparam/ |
D | coverage.txt | 14 7 YES speculative test, not in the spec !
|
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/SpeculativeExecution/ |
D | spec-compares.ll | 1 ; RUN: opt < %s -S -speculative-execution \
|
D | spec.ll | 1 ; RUN: opt < %s -S -speculative-execution \ 4 ; RUN: opt < %s -S -passes='speculative-execution' \
|
D | spec-calls.ll | 1 ; RUN: opt < %s -S -speculative-execution \
|
D | spec-fp.ll | 1 ; RUN: opt < %s -S -speculative-execution \
|
D | spec-casts.ll | 1 ; RUN: opt < %s -S -speculative-execution \
|
/external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
D | SpeculativeLoadHardening.md | 10 vulnerabilities by exploiting speculative execution in modern CPUs. These 21 The core problem of GPZ Variant #1 is that speculative execution uses branch 25 speculative execution is unwound due to being incorrect. Mispredicted paths can 109 though this code pattern may still execute speculatively, *invalid* speculative 130 * It does not completely block speculative execution, and merely prevents 148 non-speculative execution. Code dealing with this, e.g cryptographic 246 speculative store then ends up being used by the CPU during speculative 247 execution of the return, potentially directing speculative execution to 276 speculative, this will often be possible even when these are stored in 311 speculative stores. However, as most stores aren't interesting and don't [all …]
|
/external/u-boot/doc/ |
D | README.arm-caches | 33 come to the cache due to speculative memory access by the CPU. If this
|
/external/u-boot/arch/arm/cpu/armv8/zynqmp/ |
D | Kconfig | 74 This option configures MMU with no DDR to avoid speculative
|
/external/libchrome/base/process/ |
D | process_metrics.h | 347 int speculative = 0; member
|
/external/syzkaller/vendor/google.golang.org/grpc/ |
D | CONTRIBUTING.md | 17 - For speculative changes, consider opening an issue and discussing it first. If you are suggesting…
|
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/SimpleLoopUnswitch/ |
D | msan.ll | 62 ; the actual problem is in the speculative branching.
|
/external/llvm/docs/HistoricalNotes/ |
D | 2000-11-18-EarlyDesignIdeas.txt | 42 aliased, but check at runtime", like speculative execution in
|
/external/swiftshader/third_party/LLVM/docs/HistoricalNotes/ |
D | 2000-11-18-EarlyDesignIdeas.txt | 42 aliased, but check at runtime", like speculative execution in
|
123