Home
last modified time | relevance | path

Searched refs:invalidated (Results 1 – 25 of 78) sorted by relevance

1234

/llvm-project-15.0.7/clang/test/Analysis/
H A Dobjc_invalidation.m85 // Ivars invalidated by the partial invalidator.
176 // expected-warning@-2 {{Instance variable Ivar1 needs to be invalidated}}
177 // expected-warning@-3 {{Instance variable MultipleProtocols needs to be invalidated}}
178 // expected-warning@-4 {{Instance variable MultInheritance needs to be invalidated}}
179 // expected-warning@-5 {{Property SynthIvarProp needs to be invalidated or set to nil}}
180 // expected-warning@-6 {{Instance variable _Ivar3 needs to be invalidated}}
181 // expected-warning@-7 {{Instance variable _Ivar4 needs to be invalidated}}
182 // expected-warning@-8 {{Instance variable Ivar5 needs to be invalidated or set to nil}}
183 // expected-warning@-9 {{Instance variable Ivar13 needs to be invalidated or set to nil}}
321 // expected-warning@-2 {{Instance variable Ivar1 needs to be invalidated or set to nil}}
[all …]
H A Dmisc-ps-region-store-i386.m4 // Here is a case where a pointer is treated as integer, invalidated as an
H A Dmisc-ps-region-store-x86_64.m4 // Here is a case where a pointer is treated as integer, invalidated as an
H A Dretain-release-region-store.m140 // the reference count of a tracked region that was itself invalidated.
244 // The ivar binding for tc->myIvar gets invalidated.
249 // The ivar binding for tc->myIvar gets invalidated.
H A Dmisc-ps-region-store.m60 // Check our handling of fields being invalidated by function calls.
186 // Bit-fields of a struct should be invalidated when blasting the entire
262 // <rdar://problem/6914474> - Check that 'x' is invalidated because its
472 // PR 3135 - Test case that shows that a variable may get invalidated when its
569 // The call to 'bar' might cause 'q' to be invalidated.
575 // 'q' to possibly be invalidated.
590 // The call to 'bar' might cause 'q' to be invalidated.
600 // Test that the value of 'x' is considered invalidated after the block
636 // Show that we handle static variables also getting invalidated.
904 // Previously 'f' was not properly invalidated, causing the use of
/llvm-project-15.0.7/llvm/test/Transforms/LoopDistribute/
H A Dbounds-expansion-bug.ll14 ; can get earlier expanded values invalidated when casts are used. This test
15 ; ensure that we are not using the invalidated values.
36 ; new cast will be emitted and the old cast will get invalidated.
55 ; %0 = bitcast i32* %a to i8* <--- old, invalidated
64 ; %0 = bitcast i32* %c to i8* <--- old, invalidated
/llvm-project-15.0.7/llvm/test/Other/
H A Dloop-pm-invalidation.ll1 ; Test that the loop PM infrastructure is invalidated appropriately.
4 ; invalidated.
60 ; CHECK-LOOP-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
83 ; CHECK-SCEV-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
117 ; CHECK-LOOP-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
118 ; CHECK-LOOP-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
143 ; CHECK-SCEV-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
144 ; CHECK-SCEV-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
185 ; CHECK-LOOP-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
208 ; CHECK-SCEV-INV-NEXT: Clearing all analysis results for: <possibly invalidated loop>
H A Dloop-deletion-printer.ll1 ; Make sure that Loop which was invalidated by loop-deletion
12 ; DELETED: IR Dump {{.*}}LoopDeletionPass {{.*}}(invalidated)
H A Dscc-deleted-printer.ll7 ; CHECK: IR Dump After InlinerPass on (tester, foo) (invalidated)
/llvm-project-15.0.7/llvm/test/Analysis/ScalarEvolution/
H A Dinvalidation.ll1 ; Test that SCEV gets invalidated when one of its dependencies is invalidated.
4 ; due to a dependency being invalidated, and then re-urns it. This will
/llvm-project-15.0.7/llvm/docs/
H A DNewPassManager.rst279 valid and should be invalidated. If a pass wants to keep some specific
285 proper analyses invalidated.
335 cached/invalidated, you can mark the analysis manager proxy as preserved,
338 to make sure all the right analyses are invalidated.
343 By default, an analysis is invalidated if ``PreservedAnalyses`` says that
364 about the CFG, the ``FooAnalysisResult`` should not be invalidated.
366 If an analysis is stateless and generally shouldn't be invalidated, use the
380 checked if they are invalidated:
399 if the proxy itself should be invalidated. If so, that means the proxy may
408 analyses are also invalidated. This actually happens with alias analysis
[all …]
/llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/
H A Dnovect-lcssa-cfg-invalidation.ll5 ; Checks what analyses are invalidated after Loop Vectorization when no actual
11 ; CHECK: Clearing all analysis results for: <possibly invalidated loop>
/llvm-project-15.0.7/llvm/test/Transforms/CodeGenPrepare/
H A Ddom-tree.ll4 ; Checks that the dom tree is properly invalidated after an operation that will
5 ; invalidate it in CodeGenPrepare. If the domtree isn't properly invalidated,
/llvm-project-15.0.7/llvm/test/DebugInfo/X86/
H A Dinvalidated-dbg-value-is-undef.ll3 ;; Check that when a debug value is invalidated during Instruction Selection,
31 !3 = !DIFile(filename: "invalidated-dbg-value-is-undef.ll", directory: "/")
/llvm-project-15.0.7/llvm/test/Analysis/MemoryDependenceAnalysis/
H A Dinvalidation.ll1 ; Test that memdep gets invalidated when the analyses it depends on are
2 ; invalidated.
/llvm-project-15.0.7/llvm/test/Transforms/CodeGenPrepare/X86/
H A Drecursively-delete-dead-instructions.ll7 ; invalidated. This prevents the following simple loop in
/llvm-project-15.0.7/llvm/test/CodeGen/Hexagon/
H A Dexpand-condsets-def-undef.mir6 # during predication. In the code below, %2.isub_hi is invalidated
/llvm-project-15.0.7/clang/docs/analyzer/developer-docs/
H A DRegionStore.rst72 invalidated, all the instance variables must be invalidated as well. However,
99 its *contents* must also be transitively invalidated. (For example, if a region
100 ``p`` of type ``int **`` is invalidated, the contents of ``*p`` and ``**p`` may
/llvm-project-15.0.7/mlir/test/Dialect/Transform/
H A Dexpensive-checks.mlir23 …// expected-error @below {{invalidated the handle to payload operations nested in the payload oper…
/llvm-project-15.0.7/polly/test/CodeGen/
H A Dmultiple-scops-in-a-row.ll4 ; the second scop is invalidated. This test case verifies that we do not crash
/llvm-project-15.0.7/openmp/docs/remarks/
H A DOMP140.rst11 this analysis would always be invalidated by the possibility of someone calling
/llvm-project-15.0.7/llvm/test/Transforms/Attributor/ArgumentPromotion/
H A Dinvalidation.ll4 ; actually invalidated. We are using `demanded-bits` here because when printed
/llvm-project-15.0.7/llvm/test/Transforms/ArgumentPromotion/
H A Dinvalidation.ll4 ; actually invalidated. We are using `demanded-bits` here because when printed
/llvm-project-15.0.7/llvm/test/Feature/OperandBundles/
H A Ddse.ll61 ; the calling function body will be invalidated in that case, the calling
/llvm-project-15.0.7/llvm/test/Analysis/BasicAA/
H A Dinvalidation.ll1 ; Test that the BasicAA analysis gets invalidated when its dependencies go

1234