1Friday, April 22, 2005 6:17 PM 2(some stuff can be obsolete) 3============================== 4 5 6 Below are enumerated all the ASL operators 7 (32) which for now have no separate tests. 8 9 10 11 1. Intensively applied in other tests and thus 12 might be considered being already verified. 13 14 Do simple separate test for each of these 15 operators which will be the places where, 16 in the future, the additional sub-tests for 17 these operators, if any, could be located. 18 19ArgX 20LocalX 21Name 22Buffer 23String 24Store 25CopyObject 26 27 2. Indirectly verified 28 29Include 30 31 3. There is no usual way to verify them. 32 33 The tests might be either omitted or could be done 34 basing on the extension of the "memory consumption 35 instrumentation" supplying the ASL tests with the 36 required internal information. 37 38Fatal 39Notify 40 41 4. Can't be verified in our test suite 42 43Load 44Unload 45External 46LoadTable 47BreakPoint 48DefinitionBlock (each test is represented as this kind block) 49DataTableRegion 50 51 5. It is not worthy of to be definitely verified. 52 53 Do simplest test, check only that execution 54 of this operator doesn't produce exception. 55 56 17.5.83 NoOp Description: This operation has no effect. 57 58 To verify the sentence like the above definitely is too 59 complicated thing - if you have proved it for N conditions 60 it nevertheless can fail in (N+1)-th condition. The relevant 61 test should involve all the possible functionality of the 62 interpreter inserting everywhere this NoOp and verifying 63 everything each time. 64 Apparently, it is not worth the trouble. 65 It is a simple operator and it can be and should be 66 implemented with the care once. 67 68NoOp 69 70 6. Can in principle be ever in the future verified 71 (applying auxiliary script) 72 73 (see e-mail RE:Planning ACPICA validation 19.11.2004, 74 303_test_for_debug attachment for more details) 75 76Debug 77 78 7. Do the simple test, but not comprehensive 79 80 The comprehensive verification of this operator 81 could be conceived based on the following principle 82 - do replacement of all (or most of them, or at least 83 globally declared of them) the objects applied in the 84 test suite by the Aliases to them. This could be done 85 basing on the conditional #if ASL compilation which is 86 not provided now by iASL, and require the separate 87 compilation and run of the test suite. 88 89 Such the comprehensive test would actually show that 90 "AliasObject acts exactly the same as SourceObject" 91 (as far as the test suite actually provides coverage). 92 93 But we have at least one reason for the simple test, 94 but not comprehensive - there is no #if ASL ability, 95 and the second issue is either the verification of 96 this operator is worthy of the considerable and full 97 of work restructurization of the test suite. 98 99 We propose to do the simple test which use only 100 ObjectType (and SizeOf) for verification of each 101 type of SourceObject. One more checking will be 102 the overwritings with the different type object: 103 104 CopyObject(XXX, AliasObject) --> check SourceObject 105 CopyObject(XXX, SourceObject) --> check AliasObject 106 107 This operator doesn't add functionality, it is only for 108 convenience (but since provided it should be verified). 109 110Alias 111 112 8. Require the new tests designing and implementing 113 114Return 115Method 116Function 117 118Field 119BankField 120IndexField 121OperationRegion 122 123Scope 124Device 125Processor 126ThermalZone 127PowerResource 128 129 130