Searched full:correct (Results 1 – 25 of 124) sorted by relevance
12345
180 // at initial state type universe should be correct182 // initially we have correct subtyping relation195 // and finally we should have correct subtyping relation200 // note, that algorithm has not to keep subtyping relation correct during its work277 3. Algorithm implements correct subtyping closure
48 // We can't create AllocatorInfo without correct pointer to the allocator header in AllocatorInfo()106 // without initialization in the correct flow. in Initialize()
28 …upertypes intersection calculation during context merge does not lead to correct checks of compati…
39 // Atomic with release order reason: threads should see correct initialization in LockFreeBuffer()41 // Atomic with release order reason: threads should see correct initialization in LockFreeBuffer()
94 # Function to check correct usage of std primitives.106 # Function to check correct usage of memory order in atomics.
47 * `compile_commands.json` - json nija-commands file to correct execution clang-tidy.
19 movi v0, 0 # correct use: mov.null v0
54 description: Check 'lenarr' returns correct array length with array of primitives.94 …description: Check 'lenarr' returns correct array length with array of objects in Panda Assembly c…141 …description: Check 'lenarr' returns correct array length with array of objects in PandaAssembly co…294 description: Check 'lenarr' instruction with correct register number.
952 # check ObjTuple.o0 contains correct value (v0)958 # check ObjTuple.o1 contains correct value (v1)964 # check ObjTuple.o2 contains correct value (v2)970 # check ObjTuple.o3 contains correct value (v3)1083 # check ObjTuple.o0 contains correct value (v0)1089 # check ObjTuple.o1 contains correct value (v1)1095 # check ObjTuple.o2 contains correct value (v2)1101 # check ObjTuple.o3 contains correct value (v3)
1034 # check ObjTuple.o0 contains correct value (v0)1040 # check ObjTuple.o1 contains correct value (v1)1046 # check ObjTuple.o2 contains correct value (v2)1052 # check ObjTuple.o3 contains correct value (v3)1157 # check ObjTuple.o1 contains correct value (v0)1163 # check ObjTuple.o2 contains correct value (v1)
1228 description: Check 'starr.obj' with correct accumulator type in Panda Assembly context.1311 description: Check 'starr.obj' with correct accumulator type in PandaAssembly context.1534 description: Check starr.obj stores correct items into array of objects.1616 description: Check starr.obj stores correct items into array of objects.1711 description: Check starr.obj stores correct items with various types to array of objects.1788 description: Check starr.obj stores correct items with various types to array of objects.
149 description: Check ucmp.64 with correct register numbers.
22 List of methods, calls to which always be considered as correct (signature checks is turned off for…
14 # Running this test asserts correct usage of runtime option (e.g. heap-size-limit) with value > 2 GB
45 // Atomic with relaxed order reason: to correct read the value in HandleObject()72 // Atomic with relaxed order reason: to correct read the value in HandleClass()
7 …formation**) is a subset of these debug symbols which is responsible for correct **stack unwinding…
59 * Validate that object is correct from point of view of GC.81 * Validate that object (which is gc-root) is correct from point of view of GC
89 …// If yes, it is some hidden header and we have some extra header where all correct information ha…110 …// Is this memory block has some padding for alignment and we can get correct object memory addres…
140 * @return true if reference is correct and false otherwise
45 * order to capture correct locations for each of its users.
37 * **TRUE** (condition) ensure the condition is correct
57 // Though it is not semantically correct, the TypeRelationship is used in access
53 …* one is string and the other is symbol, and then check whether it is correct through th…
150 expect(postOrderVariableScopes.length == 1, "postorder array length not correct");175 expect(postOrderVariableScopes.length == 5, "postorder array length not correct");230 expect(postOrderVariableScopes.length == 6, "postorder array length not correct");
66 Edges form `Try-end` block to the catch-handlers are needed for correct linear order of basic block…