Searched refs:GEPs (Results 1 – 25 of 92) sorted by relevance
1234
| /external/swiftshader/third_party/LLVM/test/Transforms/LoopStrengthReduce/ |
| D | 2011-10-06-ReusePhi.ll | 4 ; Verify that scaled GEPs are not reused. rdar://5064068
13 ; GEPs are ugly
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/LoopStrengthReduce/ |
| D | 2011-10-06-ReusePhi.ll | 4 ; Verify that scaled GEPs are not reused. rdar://5064068
17 ; GEPs are ugly
|
| /external/llvm/test/Transforms/LoopStrengthReduce/ |
| D | 2011-10-06-ReusePhi.ll | 4 ; Verify that scaled GEPs are not reused. rdar://5064068
17 ; GEPs are ugly
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Analysis/CostModel/X86/ |
| D | gep.ll | 38 ; Check that we handle outlandishly large GEPs properly. This is unlikely to
39 ; be a valid pointer, but LLVM still generates GEPs like this sometimes in
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/LoadStoreVectorizer/X86/ |
| D | codegenprepare-produced-address-math.ll | 30 ; If and only if the loads are in a different BB from the GEPs codegenprepare
31 ; would try to turn the GEPs into math, which makes LoadStoreVectorizer's job
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/MergeFunc/ |
| D | vector-GEP-crash.ll | 2 ; This used to cause a crash when compairing the GEPs
|
| /external/llvm/test/Transforms/MergeFunc/ |
| D | vector-GEP-crash.ll | 2 ; This used to cause a crash when compairing the GEPs
|
| /external/llvm/test/Assembler/ |
| D | getelementptr.ll | 11 ; Verify that constant expression GEPs work with i84 indices.
34 ; Verify that constant expression vector GEPs work.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/Hexagon/ |
| D | common-gep-inbounds.ll | 4 ; We should generate new GEPs with "inbounds" flag.
|
| D | global-const-gep.ll | 3 ; Test that global constant GEPs are calculated correctly
|
| /external/llvm/test/Transforms/SLPVectorizer/X86/ |
| D | gep_mismatch.ll | 3 ; This code has GEPs with different index types, which should not
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/SLPVectorizer/X86/ |
| D | gep_mismatch.ll | 3 ; This code has GEPs with different index types, which should not
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/InstCombine/ |
| D | gepphigep.ll | 60 ; Check that instcombine doesn't insert GEPs before landingpad.
103 ; Check that instcombine doesn't fold GEPs into themselves through a loop
140 ; Instcombine shouldn't add new PHI nodes while folding GEPs if that will leave
|
| D | 2011-05-13-InBoundsGEP.ll | 4 ; must not discard GEPs that might overflow at runtime (aren't inbounds)
|
| /external/llvm/test/Transforms/InstCombine/ |
| D | gepphigep.ll | 60 ; Check that instcombine doesn't insert GEPs before landingpad.
103 ; Check that instcombine doesn't fold GEPs into themselves through a loop
140 ; Instcombine shouldn't add new PHI nodes while folding GEPs if that will leave
|
| D | 2011-05-13-InBoundsGEP.ll | 4 ; must not discard GEPs that might overflow at runtime (aren't inbounds)
|
| /external/swiftshader/third_party/LLVM/test/Transforms/InstCombine/ |
| D | 2011-05-13-InBoundsGEP.ll | 4 ; must not discard GEPs that might overflow at runtime (aren't inbounds)
|
| /external/llvm/docs/ |
| D | GetElementPtr.rst | 153 0`` index is needed. However, a closer inspection of how globals and GEPs work
266 What effect do address spaces have on GEPs?
311 How does VLA addressing work with GEPs?
314 GEPs don't natively support VLAs. LLVM's type system is entirely static, and GEP
374 Can I compare two values computed with GEPs?
445 As such, there are some ramifications of this for inbounds GEPs: scales implied
449 is logically treated as an unsigned value. This means that GEPs have an
499 reduces the range of possibilities for cases where two GEPs are effectively the
505 Some LLVM optimizers operate on GEPs by internally lowering them into more
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | GetElementPtr.rst | 154 0`` index is needed. However, a closer inspection of how globals and GEPs work
267 What effect do address spaces have on GEPs?
312 How does VLA addressing work with GEPs?
315 GEPs don't natively support VLAs. LLVM's type system is entirely static, and GEP
375 Can I compare two values computed with GEPs?
447 As such, there are some ramifications of this for inbounds GEPs: scales implied
451 is logically treated as an unsigned value. This means that GEPs have an
501 reduces the range of possibilities for cases where two GEPs are effectively the
507 Some LLVM optimizers operate on GEPs by internally lowering them into more
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/Scalarizer/ |
| D | vector-gep.ll | 3 ; Check that the scalarizer can handle vector GEPs with scalar indices
58 ; Check that the scalarizer can handle vector GEPs with scalar pointer
|
| /external/llvm/test/Analysis/BasicAA/ |
| D | constant-over-index.ll | 10 ; for GEPs to ignore TBAA.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Analysis/BasicAA/ |
| D | constant-over-index.ll | 10 ; for GEPs to ignore TBAA.
|
| /external/llvm/include/llvm/Transforms/Vectorize/ |
| D | SLPVectorizer.h | 109 WeakVHListMap GEPs; member
|
| /external/llvm/test/CodeGen/Hexagon/ |
| D | common-gep-basic.ll | 4 ; The mpyis from the two GEPs should be commoned out.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/Generic/ |
| D | badFoldGEP.ll | 7 ;; The code is legal but not type-safe and the two GEPs should not be folded.
|
1234