Home
last modified time | relevance | path

Searched refs:safepoint (Results 1 – 25 of 33) sorted by relevance

12

/external/llvm/test/Transforms/RewriteStatepointsForGC/
Dcodegen-cond.ll9 br i1 %rare, label %safepoint, label %continue, !prof !0
11 safepoint: ; preds = %entry
12 call void @safepoint() [ "deopt"() ]
15 continue: ; preds = %safepoint, %entry
18 ; CHECK-DAG: [ %p.relocated, %safepoint ]
36 br i1 %rare, label %safepoint, label %continue, !prof !0
38 safepoint: ; preds = %entry
39 call void @safepoint() [ "deopt"() ]
42 continue: ; preds = %safepoint, %entry
45 ; CHECK-DAG: [ %q.relocated, %safepoint ]
[all …]
Dleaf-function.ll7 ; into a safepoint. An entry safepoint should get inserted, though.
Dbase-pointers.ll38 ; Our safepoint placement pass calls removeUnreachableBlocks, which does a bunch
89 ;; Both 'next' and 'extra2' are live across the backedge safepoint...
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/RewriteStatepointsForGC/
Dcodegen-cond.ll10 br i1 %rare, label %safepoint, label %continue, !prof !0
12 safepoint: ; preds = %entry
13 call void @safepoint() [ "deopt"() ]
16 continue: ; preds = %safepoint, %entry
19 ; CHECK-DAG: [ %p.relocated, %safepoint ]
37 br i1 %rare, label %safepoint, label %continue, !prof !0
39 safepoint: ; preds = %entry
40 call void @safepoint() [ "deopt"() ]
43 continue: ; preds = %safepoint, %entry
46 ; CHECK-DAG: [ %q.relocated, %safepoint ]
[all …]
Dleaf-function.ll8 ; into a safepoint. An entry safepoint should get inserted, though.
Dbase-pointers.ll39 ; Our safepoint placement pass calls removeUnreachableBlocks, which does a bunch
90 ;; Both 'next' and 'extra2' are live across the backedge safepoint...
/external/llvm/test/Transforms/PlaceSafepoints/
Dbasic.ll4 ; Do we insert a simple entry safepoint?
13 ; On a non-gc function, we should NOT get an entry safepoint
21 ; Do we insert a backedge safepoint in a statically
38 ; to insert a backedge safepoint
Dcall-in-loop.ll2 ; don't need a safepoint poll (since the callee must contain a
Dstatepoint-frameescape.ll5 ; Do we insert the entry safepoint after the localescape intrinsic?
/external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/PlaceSafepoints/
Dbasic.ll4 ; Do we insert a simple entry safepoint?
13 ; On a non-gc function, we should NOT get an entry safepoint
21 ; Do we insert a backedge safepoint in a statically
38 ; to insert a backedge safepoint
Dlibcall.ll3 ; Libcalls will not contain a safepoint poll, so check that we insert
4 ; a safepoint in a loop containing a libcall.
Dcall-in-loop.ll2 ; don't need a safepoint poll (since the callee must contain a
Dstatepoint-frameescape.ll5 ; Do we insert the entry safepoint after the localescape intrinsic?
/external/swiftshader/third_party/llvm-7.0/llvm/test/SafepointIRVerifier/
Dbasic-use-after-reloc.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
4 ; safepoint without using the relocated value that the verifier
Dfrom-same-relocation-in-phi-nodes.ll2 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
Dunreachable-block-tolerant.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
Dcompares.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
62 ; Since the cmp can be reordered legally before the safepoint, these are correct
Duse-derived-unrelocated.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
16 ; before safepoint and one after and both have unrelocated base.
28 ; before safepoint and one after and both have unrelocated base. One of pointers
65 ; safepoint) and relocated pointer should be reported.
Dunrecorded-live-at-sp.ll1 ; RUN: opt %s -safepoint-ir-verifier-print-only -verify-safepoint-ir -S 2>&1 | FileCheck %s
Dconstant-bases.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
Duses-in-phi-nodes.ll1 ; RUN: opt -safepoint-ir-verifier-print-only -verify-safepoint-ir -S %s 2>&1 | FileCheck %s
/external/llvm/docs/
DStatepoints.rst62 #. A safepoint is a location at which pointers visible to the compiled
64 change. After the safepoint completes, the actual pointer value
68 Note that the term 'safepoint' is somewhat overloaded. It refers to
83 the compiler itself) at the safepoint,
96 reachable after the safepoint,
104 At the most abstract level, inserting a safepoint can be thought of as
130 Depending on our language we may need to allow a safepoint during the execution
138 ``%obj`` after the safepoint and update any following uses appropriately. The
157 safepoint or statepoint. The statepoint returns a token value (which
234 over the associated call safepoint even if the base is otherwise unused
[all …]
/external/swiftshader/third_party/llvm-7.0/llvm/docs/
DStatepoints.rst69 #. A safepoint is a location at which pointers visible to the compiled
71 change. After the safepoint completes, the actual pointer value
75 Note that the term 'safepoint' is somewhat overloaded. It refers to
90 the compiler itself) at the safepoint,
130 reachable after the safepoint,
138 At the most abstract level, inserting a safepoint can be thought of as
164 Depending on our language we may need to allow a safepoint during the execution
172 ``%obj`` after the safepoint and update any following uses appropriately. The
191 safepoint or statepoint. The statepoint returns a token value (which
270 over the associated call safepoint even if the base is otherwise unused
[all …]
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/X86/
Dstatepoint-forward.ll21 ;; changed at the safepoint. Forwarding a non-gc pointer value would
68 ; to know about and update that value at a safepoint. Note that the
/external/llvm/test/CodeGen/X86/
Dstatepoint-forward.ll21 ;; changed at the safepoint. Forwarding a non-gc pointer value would
68 ; to know about and update that value at a safepoint. Note that the

12