Searched refs:same (Results 1 – 25 of 35) sorted by relevance
12
2 that used to merge two array gets that have the same inputs but3 not the same type. Note that this only happens if the array is null.
3 Tracking on same thread5 Tracking on same thread, not disabling tracking
3 more exceptional conditions exist at the same time. For example,7 same time, we can only throw one or the other.
1 Regression test for optimizing that used to think 0.0 has the same bits
2 the same type, prohibited by SSAChecker.
1 Regression test to check that we do not allow registering the same dex file
2 when doing the copy on the same array.
2 calls when in the same dex file.
3 instructions from one type to the same type.
2 the same classes.dex file as MultiDex, but a different classes2.dex.
2 to the same class even in the presence of custom class loaders even after
6 17689750 GVN assigns the same value names across MONITOR_ENTER and volatile reads.
6 OptionalLong with all the same methods and fields.
5 that dvmFreeClassInnards could be called twice on the same class.
10 in the "src2" directory are compiled separately but to the same output
26 // that the image it's analyzing be the same ISA as the runtime ISA.
47 # Make sure the reference is not stored in the same vreg as used by
38 # broke the invariant of not sharing the same spill slot between those two
5 is licensed under the same terms as the file jvmti.h. The
5 is licensed under the same terms as the file jvm.h. The
29 # the compilers must do the same.
18 # // methods to ensure the 11'th target lines up to the same vtable slot as the
4 # Test multiple fields with the same name and different types.
79 - Files will always be executed in the same directory where you are executing DexFuzz.104 output. NB: if all backends crashed with the same output, this would
20 # phis are allocated to the same stack slot.