Home
last modified time | relevance | path

Searched refs:scheduling (Results 1 – 25 of 449) sorted by relevance

12345678910>>...18

/external/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_unlock/
Dcoverage.txt5 2 YES * Because the default scheduling policy is implementation
6 dependent, the case only will only demo the scheduling
/external/llvm/docs/CommandGuide/
Dlli.rst135 Disable scheduling after register allocation.
160 =none: No scheduling: breadth first sequencing
161 =simple: Simple two pass scheduling: minimize critical path and maximize processor utilization
162 =simple-noitin: Simple two pass scheduling: Same as simple except using generic latency
163 =list-burr: Bottom-up register reduction list scheduling
164 =list-tdrr: Top-down register reduction list scheduling
/external/swiftshader/third_party/llvm-7.0/llvm/docs/CommandGuide/
Dlli.rst135 Disable scheduling after register allocation.
160 =none: No scheduling: breadth first sequencing
161 =simple: Simple two pass scheduling: minimize critical path and maximize processor utilization
162 =simple-noitin: Simple two pass scheduling: Same as simple except using generic latency
163 =list-burr: Bottom-up register reduction list scheduling
164 =list-tdrr: Top-down register reduction list scheduling
Dllvm-exegesis.rst25 scheduling models. To that end, we also provide analysis of the results.
115 inconsistencies in the scheduling information. The output is an html file. For
121 Note that the scheduling class names will be resolved only when
/external/swiftshader/third_party/LLVM/docs/CommandGuide/
Dlli.pod141 Disable scheduling after register allocation.
167 =none: No scheduling: breadth first sequencing
168 =simple: Simple two pass scheduling: minimize critical path and maximize processor utilization
169 =simple-noitin: Simple two pass scheduling: Same as simple except using generic latency
170 =list-burr: Bottom-up register reduction list scheduling
171 =list-tdrr: Top-down register reduction list scheduling
/external/syzkaller/pkg/report/testdata/linux/report/
D751 TITLE: BUG: scheduling while atomic: syz-executor/ADDR
3 [ 185.479466] BUG: scheduling while atomic: syz-executor0/19425/0x00000000
/external/llvm/test/CodeGen/AArch64/
Darm64-misched-multimmo.ll8 ; Check that no scheduling dependencies are created between the paired loads and the store during p…
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/AArch64/
Darm64-misched-multimmo.ll8 ; Check that no scheduling dependencies are created between the paired loads and the store during p…
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/X86/
Dbreak-anti-dependencies.ll1 ; Without list-burr scheduling we may not see the difference in codegen here.
2 ; Use a subtarget that has post-RA scheduling enabled because the anti-dependency
/external/llvm/test/CodeGen/X86/
Dbreak-anti-dependencies.ll1 ; Without list-burr scheduling we may not see the difference in codegen here.
2 ; Use a subtarget that has post-RA scheduling enabled because the anti-dependency
/external/llvm/test/CodeGen/PowerPC/
Dtls-store2.ll26 ; works because, with new scheduling freedom, we create a copy of R3 based on the
27 ; initial scheduling, but don't coalesce it again after we move the instructions
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/PowerPC/
Dtls-store2.ll26 ; works because, with new scheduling freedom, we create a copy of R3 based on the
27 ; initial scheduling, but don't coalesce it again after we move the instructions
/external/swiftshader/third_party/llvm-7.0/llvm/include/llvm/Target/
DTargetItinerary.td10 // This file defines the target-independent scheduling interfaces
12 // itineraries for scheduling. Itineraries are details reservation
14 // in-order machine with complicated scheduling or bundling constraints.
23 // during scheduling and has an affect instruction order based on availability
DTargetSchedule.td10 // This file defines the target-independent scheduling interfaces which should
11 // be implemented by each target which is using TableGen based scheduling.
94 // that have a scheduling class (itinerary class or SchedRW list)
117 // to skip the checks for scheduling information when building LLVM for
171 // an in-order pipeline within an out-of-order core where scheduling
261 // Allow a processor to mark some scheduling classes as unsupported
264 // Allow a processor to mark some scheduling classes as single-issue.
320 // Allow a processor to mark some scheduling classes as unsupported
357 // Base class for scheduling predicates.
360 // A scheduling predicate whose logic is defined by a MCInstPredicate.
[all …]
/external/llvm/include/llvm/Target/
DTargetItinerary.td10 // This file defines the target-independent scheduling interfaces
12 // itineraries for scheduling. Itineraries are details reservation
14 // in-order machine with complicated scheduling or bundling constraints.
23 // during scheduling and has an affect instruction order based on availability
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/AMDGPU/
Dlds-output-queue.ll34 ; This is a problem for scheduling the reads from the local data share (lds).
83 ; expanding them after scheduling. Once the scheduler has better alias
85 ; scheduling.
/external/llvm/test/CodeGen/AMDGPU/
Dlds-output-queue.ll34 ; This is a problem for scheduling the reads from the local data share (lds).
83 ; expanding them after scheduling. Once the scheduler has better alias
85 ; scheduling.
/external/ltp/testcases/realtime/
D00_Descriptions.txt84 The program runs with the scheduling policy of SCHED_FIFO at a maximum
122 - The scheduling policies of threads are different from previous testcase
150 wake-up with condvars. Testcase exhibit scheduling of threads in accordance
190 - Measures scheduling jitter between realtime processes.
196 - Measures the latency involved with periodic scheduling. A thread is created
/external/swiftshader/third_party/LLVM/include/llvm/Target/
DTargetSchedule.td10 // This file defines the target-independent scheduling interfaces which should
11 // be implemented by each target which is using TableGen based scheduling.
20 // during scheduling and has an affect instruction order based on availability
/external/tensorflow/tensorflow/core/api_def/base_api/
Dapi_def_ControlTrigger.pbtxt3 summary: "Does nothing. Serves as a control trigger for scheduling."
/external/swiftshader/third_party/llvm-7.0/llvm/test/tools/llvm-mca/X86/
Dno-sched-model.s3 # CHECK: error: unable to find instruction-level scheduling information for target triple 'x86_64-u…
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/SLPVectorizer/X86/
Dschedule_budget.ll6 ; Test if the budget for the scheduling region size works.
34 ; some unrelated instructions inbetween to enlarge the scheduling region
/external/llvm/test/Transforms/SLPVectorizer/X86/
Dschedule_budget.ll6 ; Test if the budget for the scheduling region size works.
34 ; some unrelated instructions inbetween to enlarge the scheduling region
/external/ltp/testcases/realtime/func/sched_jitter/
DREADME3 This test measures scheduling jitter w/ realtime processes.
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/ARM/
Dcortex-a57-misched-vstm.ll5 ; We need second, post-ra scheduling to have VSTM instruction combined from single-stores

12345678910>>...18