-' y~ A 4rCT"T%-

SECUF 7ntered)

4 PAGE READ INSTRUCTIONS

______________________BEFORE COMPLETEING FORM1. F A D-/ '97. 550 12 GOVT ACCESSION NO. 3. RECIPIENT'S CATALOG NUMBER

4. 111Lt (ana uorw ep, 5. TYPE OF REPORT & PERIOD COVERED

Ada qompiler Validation Summary Report; Irvine 27 June 1987 to 27 June 1988

Compiler Corporation, ICC Ada Compiler,Release 4.0, HP 9000, Model 320 6. PERFORMING ORG. REPORT NUMBER

7. AUTHOR(s) 8. CONTRACT OR GRANT NUMBER(s)Wright-Patterson AFB OH 45433-6503

9. PERFORMING ORGANIZATION AND ADDRESS 10. PROGRAM ELEMENT, PROJECT. TASK

Wright-Patterson AFB OH 45433-6503 AREA & WORK UNIT NUMBERS

11. CONTROLLING OFFICE NAME AND ADDRESS 12. REPORT DATEAda Joint Program Office 27June 1987United States Department of Defense 13. NUMBER OF PAGESWashington, DC 20301-3081 36p.

14. MONITORING AGENCY NAME & ADDRESS(If different from ControllingOffice) 15. SECURITY CLASS (of this report)Wright-Patterson AFB OH 45433-6503 UNCLASSIFIED

15a. RE A8EJFICATION/DOWNGRADING

N/A

16. DISTRIBUTION STATEMENT (ofthisReport)

Approved for public release; distribution unlimited.

17. DISTRIBUTION STATEMENT (of the abstract entered in Block 20. If different from Report)

UNCLASSIFIED D I18. SUPPLEMENTARY NOTESJU 1 M

19. KEYWORDS (Continue on reverse side if necessary and identify by block number)

Ada Programming language, Ada Compiler Validation Summary Report, AdaCompiler Validation Capability, ACVC, Validation Testing, AdaValidation Office, AVO, Ada Validation Facility, AVF, ANSI/MIL-STD-1815A, Ada Joint Program Office, AJPO

20. ABSTRACT (Continue on reverse side if necessary and identify by block number)

ICC Ada Compiler, Release 4.0. Irvine Compiler Corporation, Wright-Patterson AFB, HP 9000, Model 320 under HP-UX, System V, Release 2(host and target). ACVC 1.8.

DO 'u' 1473 EDITION OF I NOV 65 IS OBSOLETE

I JAN 73 S'N 0102-LF 141-6601 UNCTASSIFIEDSECURITY CLASSIFICATION OF THIS PAGE (When Data Entered) 9

V%AVF Control Number: AVF-VSR-92. 1087 0.

87-04-07-ICC

J

Ada® COMPILERVALIDATION SUMMARY REPORT:Irvine Compiler Corporation 9

ICC Ada Compiler, Release 4.0HP 9000, Model 320

Completion of On-Site Testing: Acesion For |27 June 1987

NTIS CRA&IDTIC TAB 0UriannoincedJustificctli,, 'i

Prepared By: -Ada Validation Facility By

A S D / S C O L D ist ' lo 1 ,Ik ,C IWright-Patterson AFB OH 45433-6503 -

AvdI,1ibiiiy Co psDist vI S

Prepared For:-,,Ada Joint Program Office

United States Department of DefenseWashington, DC

®Ada is a registered trademark of the United States Government(Ada Joint Program Office).

- - ~'~ .Nrr~,1w

I

5,.,

V

Ada® Compiler Validation Summary Report: I

Compiler Name: ICC Ada Compiler, Release 4.0

Host: Target:HP 9000, Model 320 HP 9000, Model 320under HP-UX, under HP-UX,System V, Release 2 System V, Release 2

Testing Completed 27 June 1987 Using ACVC 1.8

This report has been reviewed and is approved.

Ada Validation FacilitySteven P. WilsonASD/SCOLWright-Patterson AFB OH 45433-6503

.Sa Valiaatfon Organization

Dr. John F. KramerInstitute for Defense AnalysesAlexandria VA

Ada JMnt Program OfficeVirginia L. CastorDirectorDepartment of DefenseWashington DC

!3Ada is a registered trademark of the United States Government

(Ada Joint Program Office).

w '

EXECUTIVE SUMMARY

*4li;* o~iSiiir.iar'y Report ( V. R) suuaiiax'ize.,,.i.* resnltc ,i- v! ncl .isions1.11ation testing performed on the ICC Ada Compiler, Release 1I.C, using

Vet.)t 1.3 of tYl, Ada "@ Compiler Validation Capability 'ACVC). The ICC Ada;'om,[*,.'" is hosoed on a HP 9000, Model 320 operating under HP-UX, System V,Relc P. Prog-t, n. processed luy this compileo- ,ay be iecuted w P. U".

" 'i" :i. 320 operating undo,- ,qP-TY- System V, Release ?,

:i,;ing was performud 21 Jn,. y3 ( through 2'( June 198Y al; IrvineCompi'er "'o-poration in T,-vine CA, ,inder the dir !tion or the AdaValidation Facility (AVF), according to Ada Validation Organization (AVO)policies and procedures. The AVF identified 2210 of the 2399 tests in ACVCVersion 1.8 to be processed during on-site testing of the compiler. The 19tests withdrawn at the time of validation testing, as well as the 170executable tests that make use of floating-point precision exceeding that 0supported by the implementation, were not processed. After the 2210 testswere processed, results for Class A, C, D, and E tests were ex-mincd forcorrect execution. Compilation listings for Class B tests were analyzedCor correct diagnosis of syntax and semantic errors. Compilation and linkresults of Class L tests were atialyzed for correct detection of errors.There wc .; 22 of the processed tests determined to be ina,.iplicable. Theremaining 2188 tests were passed. %

Th2 ,..ui.s of validation are summarized in the rollowing table:

iigSUlT CHAPTER COTAL2 3 4 5 6 7 8 9 10 11 12 14

Passed 102 250 334 244 161 97 137 261 124 32 218 228 2188

Failed 0 0 0 0 0 0 0 0 0 0 0 0 0 ,s'

k

Inapplicable 14 75 86 3 0 0 2 1 6 0 0 5 192 •

Withdrawn 0 5 5 0 0 1 1 2 4 0 1 0 19

TOTAL 116 330 425 247 161 98 140 264 134 32 219 233 2399

The A"F concludes that these results demonstrate acceptable conformity toANSI/MIL-STD-1815A Ada.

*)Ada is a registered trademark of the United States Government(Ada Joint Program Office).

i%,

%.

IIIJ

TABLE OF CONTENTS

CHAPTER 1 INTRODUCTION

1 1 PURPOSE OF THIS iALIDATION SUMMARY REPORT . . . . 1-21.2 USE OF THIS VATVJ'TON SUMMARY RFPORT .... . 1-21.3 REFERENCES ..... . . . . . . . . . 1-31.4 DEFINITION OZ TEI ,MS . . . . . . . . . . . .. . 1-31.5 ACVC TEST CLASSES . . . . . . . . . . . . . . . . 1-4

H APTm E . CONFIGURATION IN-'ORMAT tONS

2.1 CONFIUURATION TESTEO . . . . . . ....... . 2-12.2 IMPLEMENTATION CHARACTERISTICS . . . . . . . . . . 2-2

CHAPTER 3 TEST INFORMATION

3 TEST RESULTS . . . . . . .......... . 3-1 A'3.2 SUMMARY OF TEST RESULTS BY CLASS ......... 3-13.3 SUMMARY OF TEST RESULTS BY CHAPTER . . . ... 3-23.4 WITHDRAWN TESTS ..... . . . . . . . . . . 3-23.5 INAPPLICABLE TESTS .................... 3-23.6 SPLIT TESTS ... .. . ... .. . . . .3-33.7 ADDITIONAL TESTING INFORMATION . . .. ..... 3-43.7.1 Prevalidation ......... . . . . . . . . 33.7.2 Test Method ..... . . . . . . . . . . . 3-43.7.3 Test Site . . . . . . . . . . . .... 3-5

APPENDITX A DECLARATION OF CONFORMANCE

APPEND X B APPENDIX F OF THE Ada STANDARD

APPENDIX C TEST PARAMETERS

APPENDIX D WITHDRAWN TESTS

x

-N ..' .

S'V

.

CHAPTER 1

INTRODUCTION

2 us ialidation Summary Repor }V.6lbf describes the l-xtent to which aspecific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A.This report explains all technical terms used within it and thoroughlyreports the results o ting this compiler using the Ada CompilerValidation Capability A4-XGJ) An Ada compiler must be implementedaccording to the Ada Standard, and any implementation-dependent featuresmust conform to the requirements of the Ada Standard. The Ada Standardmust be implemented in its entirety, and nothing can be implemented that isnot in the Standard,

-ven though all validated Ada complie s conform to the Ada Standard, it,aust be understood that some differences do exist between implementations.The Ada Standard permits some implementation dependencies--for example, themaximum length e-f identifiers or the m~iximum values of integer typ.,s..Other differences betwcen compilers result from characteristics ofparticular operating systems, hardware, or implementation strategies. Allof the dependencies observed during the process of testing this compilerare given in this report.

The information in this report is derived from the test results producedduring validation testing. The validation process includes submitting asuite of standardized tests, the ACVC, as inputs to an Ada compiler andevaluating the results. The purpose of validating is to ensure conformityof the compiler to the Ada Standard by testing that the compiler properlyimplements legal language constructs and that it identifies and rejectsillegal language constructs. The testing also identifies behavior that isimplementation dependent but permitted by the Ada Standard. Six classes oftests are used. These tests are designed to perform checks at compiletime, at link time, and during execution.

1-1S

INTRODUCTION

1.1 PURPOSE OF THIS VALIDATION SUMMARY REPORT

This VSR documents the results of the validation testing performed on anAda compiler. Testing was carried out for the following purposes:

* To attempt to identify any language constructs supported by thecompiler that do not nonfor'm to the Ada Standard

To dttempt to Ldentify any unstippored lan6 -k, .:os.t ructsrequired by the Ada Standar-d

* To determine that the implementation-dependent - behavior is allowedby the Ada Standard

S

i. i of iut ,,i compilet- ,ias conducted by SofTech, Ino,,, under thedii f'Lion ou' the AVF acoording to policies and 5j.ocedures established bytht, Ada Validation Organization (AVO). On-site testing was conducted from21 oTAe 1987 through 27 June 1987 at Irvine Compiler Corporation in IrvineCA.

1.2 USE OF THIS VALIDATION SUMMARY REPORT

Co si'.tent with the national lawn of the originating country, the AVO maymake full and free public disclosure of this report. In the United States,,Ahis is provided in accordance with the "Freedom of Information Act" (5,!.S.C. #552). The results of this validation apply only to tho computers,operating systems, and compiler versions identified in this report.

i'h- organizations represented on the signature page of this report do notr'epresent or warrant that all statements set forth in this report areaccurate and complete, or that the subject compiler has no nonconformitiesto the Ada Standard other than those presented. Copies of this report areavailable to the public from:

Ada Information ClearinghouseAda Joint Program Office 0OUSDREThe Pentagon, Rm 3D-139 (Fern Street)Washington DC 20301-3081

or from:

Ada Validation FacilityASD/SCOL i!Wright-Patterson AFB OH 45433-6503

1-2

N.5A

V-7 Z.4 K_ -71V T. W7-W K-1 1" IV" T

INTRODUCTION

Questions regarding this report or the validation test results should bedirected to the AVF listed above or to: S

Ada Validation OrganizationInstitute for Defense Analyses1801 North Beauregard Street41,xandria VA 22311

3 9J EFERENCES

I . Referenc iawual for the Ada P roamninl Lauage,ANSI/MIL-STD-1815A, Februacy - 19 33.

2. Ada Validation Organization: Procedures and Guidelines, Ada JointProgram Office, 1 January 1987.

3. Ada Compiler Validation Capability Implementers' Guide, SofTech,Inc., December 1984.

1. 4 UEFINITION OF TERMS

ACVC The Ada Compiler Validation Capability. A set of programsthat evaluates the conformity of a compiler to the Adalanguage specification, ANSI/MIL-STD-1815A.

Ada Standard ANSI/MTL-STD-1815A, February 1983.

Applicant The agency requesting validation.

AVF The Ada Validation Facility. In the context of this report, Ithe AVF is responsible for conducting compiler validationsaccording to established policies and procedures.

AVO The Ada Validation Organization. In the context of thisreport, the AVO is responsible for setting procedures forcompiler validations.

Compiler A processor for the Ada language. In the context of thisreport, a compiler is any language processor, includingcross-compilers, translators, and interpreters.

Failed test A test for which the compiler generates a result thatdemonstrates nonconformity to the Ada Standard.

Host The computer on which the compiler resides.

1-3

* *~ p~ ~r 45~ V W ~ ~ V b

INTRODUCTION

Inapplicable A test that uses features of the language that a compiler istest not required to support or may legitimately support in a way

other than the one expected by the test. S

Passed test A test for which a compil pr generates the expected result.

Target The computer foi' which a compiler gonerates code.

A program thatU z.hecks k ,upi'.cr's conf ,cLy regarding aparticular feature ' te'atures to the Ada Stanidard. In thecontext -f this repor., ,;e term i . used to designate asingle teit., .hich may ompr.rise one or more files.

WW114.iwn A test fouai ;*,) )e .LncorrecL dnd 00t tid .o G;,IcCk confoi.ftnyto the Ada3 lan :3.3ge sp, fio-tioa. A t: .st may be incor'. t Sbecause it ha:i in invalid rest o0 (c-t.Lve, fails to mee is .test objective, or contal.riu illegal or erroneous use of thelanguage.

1.5 ACVC TEST CLASSES

Conformity to the Ada Standard is measured using the ACVC. The ACVC.ontains both legal and illegal Ada programs structured into six testcli.:3ies: A, B, C, D, E, and L. The first letter of a test name identifiesthe .* lass to whi.ch it belongs. Class A, C, D, and E tests are executable, -and .pecial program units are used to report their results duringex: . on. (..Lass B tests are expected to produce compilation errors.ClaM L tests are expected to produce link errors.

Clas3 A tests check that legal Ada programs can be successfully compiledand executed. However, no checks ar performed during execution to see ifthe test objective has been met. For example, a Class A test checks that %reserved words of another language (other than those already reserved inthe Ada language) are not treated as reserved words by an Ada compiler. AClass A test is passed if no errors are detected at compile time and theprogram executes to produce a PASSED message.

Class B tests check that a compiler detects illegal language usage. ClassB tests are not executable. Each test in this class is compiled and theresulting compilation listing is examined to verify that every syntax orsemantic error in the test is detected. A Class B test is passed if everyillegal construct that it contains is detected by the compiler. .

Class C tests check that legal Ada programs can be correctly compiled andexecuted. Each Class C test is self-checking and produces a PASSED,FAILED, or NOT APPLICABLE message indicating the result when it isexecuted.

Class D tests check the compilation and execution capacities of a compiler. •Since there are no capacity requirements placed on a compiler by the AdaStandard for some parameters--for example, the number of identifiers

1-4

1 f _. L: ' ,'4 S.; ' ' '.'

INTRODUCTION

permitted in a compilation or the number of units in a library--a compilermay refuse to compile a Class D test and still be a conforming compiler.Therefore, if a Class D test fails to compile because the capacity of thecompiler is exceeded, the test is classified as inapplicable. If a Class Dtest compiles successfully, it is self-checking and produces a PASSED orFAILED message during Rxecution

Ct -.at is -3If -checkft ~ ins afol nc .tzK ,T tiAiPASSFID,.r 'A.WE) mtsslge 'hen it is .'..t. . ex' c.ed. However, ?he Ada

AtN jdard permits an imnplementatio. to I -,t programs containi,16 somefeatures addre,.,cd by Clas- - tests during uwpilation. rherefor;-, a ClassF test is pasnq 'y. a compileot if Lt i i rcompiled successfully aod executes

*,) produce a PAS':i'D miP:sage, or if 1t. Is rejected by the i.c-nniler for an1 i,.wable reason.

. L "asts check that incom.lete oo illegal Ida programs involving %multiple, separately compiled units are detected and not allowed toexecute. Class L tests are compiled separately qnd execution is attempted.A Class L test passes if it is rejected at link time--that is, an attemptto execute the main program must generate an error message before anydeclarations in the main program or any units referenced by the mainprogram are elaborated.

Two library units, the package REPORT and the procedure CHECKFILE, supportthe aelf-checking features of the executable tests. The package REPORTprov;..les the mechanism Ly whi-ch executable tests report PASSED, FAILED, or

NOT APPLICABLE results. It also provides a set of identity functions usedto deieat some compiler optimizations allowed by the Ada Standard thatwouW6 ,ircumvent a Lest objective. The procedure CHECK FILE is used toc1heuk the contents of text file!. written by some of the Class C tests forchapter 14 of the Ada Standard. The operation of these units is checked bya set of executable tests. T*hese tests produce messages th&A are examinedto verify that the units are operating correctly. If these units are notoperating correctly, then the validation is not attempted.

The text of the tests in the ACVC follows conventions that are intended toensure that the tests are reasonably portable without modification. Forexample, the tests make use of only the basic set of 55 characters, containlines with a maximum length of 72 characters, use small numeric values, andplace features that may not be supported by all implementations in separatetests. However, some tests contain values that require the test to becustomized according to implementation-specific values--for example, anillegal file name. A list of the values used for this validation isprovided in Appendix C.

A compiler must correctly process each of the tests in the suite and ?demonstrate conformity to the Ada Standard by either meeting the passcriteria given for the test or by showing that the test is inapplicable tothe implementation. The applicability of a test to an implementation isconsidered each time the implementation is validated. A test that isinapplicable for one validation is not necessarily inapplicable for asubsequent validation. %

1-5

INTRODUCTION

Any test that was determined to contain an illegal language construct or anerroneous language construct is withdrawn from the ACVC and, therefore, isnot used in testing a compiler. The tests withdrawn at the time ofvalidation are given in Appendix D.

1-6[

V.

°:

4.

pN

' !p

I1-6

X V7 -v W 7KW7 W W' 17

' 'V

CHAPTE i 2

UONFIGIiRATTON tNFU;RMATL'' ..-a

2.1 CONFIGURATION TESTED

The candidate compilation system for this validation was tested under the

following configuration:

Compiler: ICC Ada Compiler, Release 4.0

ACVC Version: 1.8

,rtificate Number: 870622W1.08100 P

Host Computer':

Machi.ne: iP 9000, Model 320

Operating System: HP-UXSystem V, Release 2

Memory Size: 4 megabytes '

Target Computer:

Machine: HP 9000, Model 320

Operating System: HP-UXSystem V, Release 2

Memory Size: 4 megabytes

2-1

CONFIGURATION INFORMATION

2.2 IMPLEMENTATION CHARACTERISTICS

One of the purposes of validating compilers is to determine the behavior ofa compiler in those areas of the Ada Standard that permit implementationsto differ. Class D and E tests specifically check for such implementationdifferences. However, tests in other classes also characterize animplementation. This compiler is characterized by the followingtrn'F"pretations of the Aia Standard:

Capacities.

'he compiler corree,;.y .processes tests containing loop sLatemnnts.e9ted to 65 liels; block statements nested to 65 levels, andrecroive prooeduL' 3 eprirately compilnd as subA.iV nested to 17t , is. It corcec [y processes a compilation containing 723v kables in the ime declarative part. (See tests D5103A..H (8tests), D56001B, D64005E..G (3 tests), and D29002K.)

Universal integer calculations.

An implementation is allowed to reject universal integercalculations having values that exceed SYSTEM.MAX INT. Thisimplementation does not reject such calculations and processesthem correctly. (See tests D4A002A, D4AOO2B, D4AO04A, andD4A004B.)

• PredeCined types.

Th.3 implementation supports the additional predefined typesSHORT' INTEGER and TINY INTEGER in the package STANDARD. (Seetests B86001C and B86001D.)

. Based literals.

An implementation is allowed to reject a based literal with avalue exceeding SYSTEM.MAX INT during compilation, or it may raise lk

NUMERIC ERROR or CONSTRAINT ERROR during execution. Thisimplementation raises NUMERIC ERROR during execution. (See testE24101A.)

• Array types. •

An implementation is allowed to raise NUMERIC ERROR orCONSTRAINT ERROR for an array having a 'LENGTH that exceedsSTANDARD. INTEGER' LAST and/or SYSTEM.MAXINT.

2-2

C, X .7. 1k. X

CONFIGURATION INFORMATION

A packed BOOLEAN array having a 'LENGTH exceeding INTEGER'LASTraises STORAGE ERROR when the array objects are declared. (Seetest C52103X.)

A packed two-dimensional BOOLEAN array with more than INTEGER'LASTcomponents raises CONSTRAINT ERROR when the length of a dimensionis calculated and exceeds INTEGER'LAST. (See test C52104Y.)

A null array with ni dimension of length greater tanINTEGER' LAST may ra;.ae 14UMERIC ERROR or CONSTRAINT ERROR eitherwhen deoli-'ed ocv assigned. Alternatively, an implementation mayaccept 1'P de(-aration. Howe'. er, !:ngths must match i.i arrayslice assignments. This ImplemenLation dous not raise anexception. (See test E52103Y.) S

In ass bt'ing one-dimensional array types, the expces iion appearsto be evaluated in its entirety before CONSTRAINT _RROR is raisedwhen checking whether the expression's subtype is compatible withthe target's subtype. In assigning two-dimensional array types,the expression appears to be evaluated in its entirety beforeCONSTRAINTERROR is raised when checking whether the expression's Rsubtype is compatible with the target's subtype. (See testC52013A.)

Discriminated types.

During compilation, an implementation is allowed to either acceptor reject an incomplete type with dLscriminants that i%13ed !.n anaccess type definition with a owpatible discriminant constraint.This implementation accepts such subtype indications. (See testE38104A.)

In assigning record types with discriminants, the expressionappears to be evaluated in its entirety before CONSTRAINT ERROR israised when checking whether the expression's subtype iscompatible with the target's subtype. (See test C52013A.)

Aggregates.

In the evaluation of a multi-dimensional aggregate, index subtype ',

checks appear to be made as choices are evaluated. (See testsC43207A and C43207B.)

In the evaluation of an aggregate containing subaggregates, allchoices are not evaluated before being checked for identicalbounds. (See test E43212B.)

All choices are not evaluated before CONSTRAINT ERROR is raised ifa bound in a nonnull range of a nonnull aggregate does not belong Sto an index subtype. (See test E43211B.)

2-3

po

CONFIGURATION INFORMATION

Functions.

An implementation may allow the declaration of a parameterlessfunction and an enumeration literal having the same profile in thesame immediate scope, or it may reject the function declaration.If it accepts the function declaration, the use of the en<nera ionliteral's identifier denotes 'the finction. This implementztionrejects the declaration. (See t,.t.* E66001D.)

Representation clauses.

ihz3 Ada Standard doeb not requit -An implementation o .upportc a *sentation clauses. If a r o'esentation ilause is not

:)ijported, then the implementation must rejeA it. While theop-jration of representation clauu.es is not checked by lersion 1.8of the ACVC, they are used in testing other language features.This implementation accep's 'SIZE. It rejects 'STORAGESIZE forcollections and 'SMALL clauses. Enumeration representation

clauses, including those that specify noncontiguous values, appearto be supported. (See tests C55B16A, C87B62A, C87B62B, C87B62C,and BC1002A.)

Pragmas.

The pragma INLINE is not supported for procedures or functions.(See tests CA3OO42 and CA3004F.)

Input/output.

The package SEQUENTIAL 10 cannot be instantiated withunconstrained array types and record types with discriminants.The package DIRECT_10 cannot be instantiated with unconstrainedarray types and record types with discriminants without defaults.(See tests AE2101C, AE2101H, CE2201D, CE2201E, and CE2401D.)

An existing text file can be opened in OUT-FILE mode and can becreated in both OUT FILE and INFILE modes. (See test EE3102C.)

More than one internal file can be associated with each external ",

file for text I/O for both reading and writing. (See testsCE3111A..E (5 tests).)

More than one internal file can be associated with each externalfile for sequential I/O for both reading and writing. (See testsCE2107A..F (6 tests).)

More than one internal file can be associated with each externalfile for direct I/O for both reading and writing. (See testsCE2107A..F (6 tests).)

2-4

CONFIGURATION INFORMATION

An external file associated with more than one internal file canbe deleted. (See test CE2110B.)

Temporary sequential files are given a name. Temporary directfiles are given a name. Temporary files given names are deletedwhen they are closed. (See tests CE2108A and CE2108C.)

Genercs.

Generic subprogram declarations and bodies can be compi.led inseparate cop lations (Se -, -3,12009F.)

Generic pa,-1kage declarations afid Wodies can be compiled in5eparate compilations. (See tests ,-A?009C and BC3205D.)

1

2-5

5 LA

'I

C14APTER 3

TEST TNFOPMATION

J,) TEST RESULTS

Version 1.8 of the ACVC contains 2399 tests. When validation testing ofICC Ada Compiler was performed, 19 tests had been withdrawn. The remaining2380 tests were potentially applicable to this validation. The AVFdetermined that 192 tests were inapplicable to this implementation, andthat the 2188 applicable tests were passed by the implementation.

The AVF concludes that the testing results demonstrate acceptable,onformity to the Ada Standard.

3.2 SUMMARY OF TEST RESULTS BY CLASS

RESULT TEST CLASS TOTALA B C D E L

Passed 67 865 1184 17 11 44 2188

Failed 0 0 0 0 0 0 0

Inapplicable 2 2 184 0 2 2 192

Withdrawn 0 7 12 0 0 0 19

TOTAL 69 874 1380 17 13 46 2399

3-1

I

TEST INFORMATION

3.3 SUMMARY OF TEST RESULTS BY CHAPTER .4

RESULT CHAPTER TOTAL2 3 4 5 6 7 8 9 10 11 12 14 -

1assed 0n? 250 334 244 161 9( -37 61 1214 32 21:3228 2188

Failed 0 0 0 0 U 0 0 0 0 1 0 0 0

fnapplicabl.c 14 75 86 3 0 0 2 1 6 '3 ? 5 192

'ithdrawn 0 5 5 0 0 1 1 2 4 0 1 0 19i6 330 425 247 161 98 140 J-4 134 32 219 233 2399

3.4 WITHDRAWN TESTS

The following 19 tests were withdrawn from ACVC Version 1.8 at the time ofthis validation:

C32114A C41404A B74101B BC3204CB33203C B45116A C87B50AC34018A C48008A C92005AC35904A B49006A C940ACAB37401A B4AO1OC CA3005A..D (. tests)

neo ltopndix D for the reason that each of these tests was withdrawn.

3.5 INAPPLICABLE TESTS .

Some tests do not apply to all compilers because they make use of featuresthat a compiler is not required by the Ada Standard to support. Others maydepend on the result of another test that is either inapplicable orwithdrawn. The applicability of a test to an implementation is consideredeach time a validation is attempted. A test that is inapplicable for onevalidation attempt is not necessarily inapplicable for a subsequentattempt. For this validation attempt, 192 tests were inapplicable for thereasons indicated:

. C34001E, B52004D, B55BO9C, and C55BO7A use LONG INTEGER which isnot supported by this compiler.

. C34001F and C35702A use SHORTFLOAT which is not supported by thiscompiler.

3-2

**4 - , * * , - ; 4 *, '.'- VJ V ",, \.VVV . ' %...V V '- ?. */- -'-"-' V ' , :'' '

TEST INFORMATION

" C34001G and C35702B use LONG FLOAT which is not supported by thiscompiler.

" C87B62B..C (2 tests) use the length clauses 'STORAGESIZE foraccess types and 'SMALL which are not supported by this compiler.The length clause is rejected during compilation.

" C96005B checks implemetaiLons for which the smallent and largestvalues it ty, DURATION are eii'ferent from the smallest andlargest :o , D1JRA.Ti)!'s b; ia: type. This is not the cas, forthis imploiient.atif.on.

CA3004E, !A3OO4C, and LA30O041 use INLINE pragma c Do, 0u:'Cs.hi.ch is ,- ) qupported by this compiler. %%

CA3004F, EA-. -.4D, and LA3004B use INLINE pragma uvo funct ionswhich i . not supported by thi s compiler.

* AE2101C, CE2201D, and CE2201E use an instantiation of packageSEQUENTIAL_10 with unconstrained array types which is notsupported by this compiler.

* AE2101H and CE2401D use an instantiation of package DIRECT 10 withunconstrained array types which is not supported by this compiler.

* The following 170 tests require a floating-point accuracy thatexceeds the maximum of 15 suppot',?ed by the implementation:

C24113L..Y (14 tests) C35708..Y (14 tests) C45421L..Y (14 tests)C35705L..Y (14 tests) C35802L..Y (14 tests) C45424L..Y (14 tests)C35706L..Y (14 tests) C45241L..Y (14 tests) C45521L..Z (15 tests)

C35707L..Y (14 tests) C45321L..Y (14 tests) C45621L..Z (15 tests)

3.6 SPLIT TESTS

If one or more errors do not appear to have been detected in a Class B testbecause of compiler error recovery, then the test is split into a set of

smaller tests that contain the undetected errors. These splits are thencompiled and examined. The splitting process continues until all errorsare detected by the compiler or until there is exactly one error per split.Any Class A, Class C, or Class E test that cannot be compiled and executedbecause of its size is split into a set of smaller subtests that can beprocessed. -

Splits were required for three Class B tests:

B59001A B59001E B85013C -U

3-3 1

TEST INFORMATION

3.7 ADDITIONAL TESTING INFORMATION

3.7.1 Prevalidation

Pri) to validation, a set of test results for ACVC Version 1.8 produced bythe !CC Ada r,,qp ler was submitted to the AVF by the applicant for review.

.~y "~Of I..hese :es , ,.-iontc::' :d that thn 4nopiler succe-sful ly;d Ik. applicabl) '.ests, and that the compiler, .xhibi.'P , The pected

o, all inapplicable tests.

; ',st Method

1 'A.1 n t,,f the ICC Ada Compiler using ACVC Version 1.8 was conductedon-site by a validation team from the AVF. The configuration consisted ofa PP 9000, Model 320 operating imder HP-UX, System V, Release 2.

A magnetic tape containing all tests except for withdrawn tests and testsrequiring unsupported floating-point precisions was taken on-site by thevalidation team for processing. Tests that make use ofimplementation-specific values were customi-,ed 'before being written to themagnetic tape. Tests requiring splits during the prevalidation testingwere included in their split form on the magnetic tape.

"he *(lnteats of the magnetic tape were riot loaded directly onto the hostcomputer, The tests were loaded onto a ISl Optimum V and transferred tothe HP ,vi ethernet. After the test files were loaded to disk, the full

set of tests was compiled and linked on the HP 9000, Model 320 and allexecutabLe tests were run. Results were printed after they weretran*,,r'ed to a Gould 6050 via a RS232.

The compiler was tested using command scripts provided by Irvine Compiler

Corporation and reviewed by the validation team. The following optionswere in effect for testing:

Option EffectI

-LIST produces a list file-QUIET turns off messages to console-STACK CHECK adds code to check stack size for tasks

Tests were compiled, linked, and executed (as appropriate) using one

computer. Test output and compilation listings were captured on magnetictape and archived at the AVF. The listings examined on-site by thevalidation team were also archived. %

3-4

• ", " -,,' m' , " ",, " ",

TEST INFORMATION

3.7.3 Test Site

The validation team arrived at Irvine Compiler Corporation in Irvine CA on21 June 1987, and departed after testing was completed on 27 June 1987.

3-5,

*1

f..t't..

f..1

3-5

A.PP NDIX A

DRCL AATT .W1J CONFORMANCE

Irvine Compi.lor Corporation han submitted th, followingDeclaration of Conformance concerning the ICC AdaCompiler. I

A

A-1

DECLARATION OF CONFORMANCE

Compiler Implementor: Irvine Compiler CorporationAda Validation Facility: ASD/SCOL, Wright-Patterson AFB, OHAda Compiler Validation Capability (ACVC) Version: 1.8

Base Configuration

&-,,t umpiler Name: 'CC Ad Coapiler Versirin: Rtelaase 4.oHos'. Architecture ISA: HP 9000, Model 320 OS&4 2 #: HP-JA, System V,

Release 2TarvA lrchit. tlwe rSA: HP 9000, Model 320 OS&VER #: HP-UX, Syst, m V,

Release 2

ImplemanY)z' ,s Duolaivation

I, the undersigned, representing Irvine Compiler Corporation, haveimplemented no deliberate extensions to the Ada Language StandardANSI/MIL-STD-1815A in the compiler(s) listed in this declaration. Ideclare that Irvine Compiler Corporation is the owner of record of the Adalanguage compiler(s) listed above and, as such, is responsible formaintaining said compiler(s) in confornnnce to ANSI/MIL-STD-1P15A. All p

certificates and registrations for Ada language compiler(s) listed in thisdeclaration shall be made only in the owner's corporate name.

LDate: T4 - ??

?Wit3ne compiler CorporationDan Eilers, President

Owner's Declaration

I, the undersigned, representing Irvine Compiler Corporation, take fullresponsibility for implementation and maintenance of the Ada cumpiler(s)listed above, and agree to the public disclosure of the final Validation %Summary Report. I further agree to continue to comply with the Adatrademark policy, as defined by the Ada Joint Program Office. I declarethat all of the Ada language compilers listed, and their host/targetperformance are in compliance with the Ada Language StandardANSI/MIL-STD-1815A.

__ __ _ __ __ _ __ __ _Date: -j_.. Z ' ?Irvine Compiler CorporationDan Eilers, President

"Ada is a registered trademark of the United States Government

(Ada Joint Program Office).

A-2

APPENDIX B

AP'PENDIX F' OF P{LT R 4 1,DARD.

i: tKy allowed implenntation depeodencies correspond to implementation-dependent pragmas, to certain machine-dependent conventions as mentioned inchapter 13 of MIL-STD-1815A, and to certain allowed restrictions on

representation cikuses. The implementation-dependent characteristics ofthe ICC Ada Compiler, Release 4.0, are described in the following sectionswhich discuss topics in Appendix F of the Ada Language Reference Manual(ANSI/MIL-STD-1815A). Implementation-specific portions of the packageSTANDARD are also included in this appendix.

packagei STANDARY is

type INTEGER is range -2147483648 .. 214483647;type SHOill' INTEGER is range -32768 .. 32767;type TINY_NTEGER in range -128 .. 127;

type FLOAT is digits 15 range-2.24711641857789E+307 .. 2.24711641857789E+307;

type DURATION is delta 2.44140625E range -524287.0 .. 524287.0;

end STANDAPD;

'V

B-1 •

% % V V,

k4

S

AppendlL F.CC Ada Implementation

[St Optimum 'V [SI 4.2BSJ) RWie .U5SUN 350 / SUN 4.21,3SD uit'TX SAT&T 3B2 / UNIX System V.3

HP9000 / HP-UX 5.2

Irvine Compiler Corporation18021 Sky Park Circle, Suite L S

Irvine, CA 92714(714) 250-,366 .

May 28, [987

1 ICC Ada Implementation

The Ada language definition allows certain dkiferences between compilers. Thissection describes the implementation-depcndent characteristics of TCC Ada.2 Pragmas

The following pragmas are added by ICC:

Export This pragma is a complement to the predefined pragma interface. Itenables subprograms written in Ada to be called from other languages. •It takes 2 or 3 arguments. The first is the language to be called from,the second is the subprogram name, and the third is an optional stringdesignating the actual subprogram name to be used by the linker. Thispragma must appear prior to the body of the designated subprogram.

Compress This pragna is a complement to the representation clause size. Ittakes the name of a discrete subtype as the single argument, and specifiesthat the subtype should be represented as compactly as possible, regard--%less of the .,!presentation of the subtype's base type. This pragma must %appear prior to any reference to the named subtype.

B-2

tee le

ICC Ada Implementation - Appendix F

Put, Put- lirte These pragnas take arty number of arguments and write their

• ,alue to st~nd.-trd out, ;t compile !:.te -vhe~n enco,,nti-.d by thi, coir'.,Rer. 1,i .7-g' ,_,8 111a, .' . , bet ap.,/ ;,hl , i,' a t-lon. ,or l

; Lteger 1 1,- , vv.'.ose value is known at c .-.:,.L ., 'ragma P ~ i,Wdds a cart i;!ge return after printing all ,f '; -! vguments. These pragma~saxe often , f i. conjunction with conditional compilation. They mayappear At, ", i pragma is allowAed.

'Th-, fo!lovilo : -. 6 dt,-.ed oragmw 'i.wi been exte ,,O, by [CC. 1

Interface This .,, zma w ..t ,.ved to 4.,,~ ~ .iables in addition to sub ,pco- ,

pais. It is ak;-) allo~ved to hav. 4A. option ,I third parameter which L astring designating the name for the linker to use to reference the variableor subprogram.

Suppress In addition to suppressing the standard checks, ICC also permits

suppressing the following: e,

exception- info Suppressing exception- inf'o improves run-time perfor-

mance by reducing the amount of information maintained for mes-sages that appeaxr when exceptions are propagated out of the main,'pr.,ra.Tn or any task. '

all..,c: i,.cks Suppressing all- checks suppreises all the standat, I checks as--well as exception- info.

3 Preprocessor Directives'

ICC Ada incorporates an integrated preprocessor whose directives be , withthe keyword Pragma. They are as follows: .,

If, Elsif, Else, End If These preprocessor directives provide a conditionalcompilatior mechanism. f

Include This preprocessor directive provides a compile-time source file inclu-sion mechanism. It is integrated with the library management and auto- .matic recompilation facilities.

4 Input/Output Facilities

4.1

The implementation dependent specifications from TEXT- 10 and DIRECT- IS10.

are:

type COUNT is rang* 0 .. iteger'laut;

subtype FIELD is INTEGER range 0 intoger'last;

.

B-3-

A

ICC Ada Implementation - Appendix F

4.2 FORM Parameter!CG a implement the FORM . i aneter to .. e procedures OPEN and ("tE-ATE in DIRECTIO, SEQU'' TAL..IO, and '.'EXT..IO to performn avariety ofancilhry f,nctions. The FORM parameter is ;\ string literal crntain':.? parame-ters in the style of named paraiet- iotation.. In general the FORM p 'rarneterhas dr '.-,uwing format:

'fieldL => "a'idu"i :, fieRd, : ,,e ]

where f eld, => valuei can be

OPTION => NORMALOPTION => APPENDPAGE-MARKERS => TRUEPAGE-MARKERS => FALSEREAD-INCOMPLETE => TRUEREAD-INCOMPLETE => FALSEMASK => <9 character protection mask>

Each field is separated from its value with a "=>" and each field/value pairis separated by a comma. Spaces may be added anywhere between tokens andupper-case/lower-case is insignifi,:ant. For examplo"

3optloa -> append. PAGE-MARKERS a> FALSE. Mask -> rvxwrx---');

The interpretation of the fields and their values is presented below.

OPTION Files may be OPENed for appendage. This causes data to be ap-pended directly onto the end of an existing file. The default is NORMAL "which overwrites existing data. This field applies to OPEN in all three ,standard I/O packages. It has no effect if applied to procedure CREATE.

PAGE-MARKERS If TRUE then all TEXTIO routines dealing with pageterminators are disabled. They can be called, they simply do not doanything. In addition the page terminator character ('L) is allowed to beread with GET and GET.LINE. The default is TRUE which leaves pageterminators active.

READ-INCOMPLETE This field applies only to DIRECT.IO and SE- IQUENTIAL.IO and informs the package about what should be done withreads of incomplete records. Normally, if a READ is attempted and thereis not enough data in the file for a complete record, then ENDERROR 'or DATA-ERROR will be raised. By setting READ-INCOMPLETE toTRUE, an incomplete record will be rcad successfully and the remaining

B-4

p

ICC Ada Lmplementation - Appendix F b

bytes in the record will be zeroed. Attempting a read after the last in-complete record will raise END.ERROR. The SIZE function will reflectthe fact that ther is :-. e more rec nd when the Ix-t recrw is complete

and READ- (NCCOMPLETE I- 'RjJE.

MASK -et a protection ni.k tu . oOrol accesi to a file. The inask is a Stan-d. nine character strig notation used by TJN EX. The letters cannot berea,rAnge'l or deleted so that the string is alwA, -x-tly nine characleislong. ".bli tpplies to CREATE in all 'iree , ndard 1/10 package,! The -defa,: :i 4:%termined at runtime by ti.e aser's envicolment settig:.

If a syntax error is encountered with.kii the FORM4 parameter the, .. : excep-tion USE-ERROR is raised at the OPEN or CREATE call Also, the standardfunction TEXT-IO.FORM returns the current setting of the form fields, incl-rbing default values, as a single string.

5 Line Length

The maximum line length is 254 characters.

6 Numeric Types

ICC Ada supports three predefined integer types:

TINY-INTEGER -128.. 127 8 1.tsINTEGER -32768..32767 16 bitsLONG-INTiGER -2147483648..2147483647 32 bits

Unsigned tiny and short integer types are available via the SIZE representationclause. -

Type float is available.

Attribute FLOAT valuesize 64 bits Sdigits 15first -2.24711641857789E + 307last +2.24711641857789E + 307

7 Tasks

The type DURATION is defined with the following characteristics:

B-5

%S

ICC Ada Implementation - Appendix F

Attribute DURATION valuedelta 2.44140625E - 04 secsmall 2.. 11. 0675E . 04 socfirst 524287.0 seclast i24-1.'1.0 sec

Thi iubtype SYSTEM.PRIORITY as defiatd p-i-ides the following range:

Attribute PPIORITY walue- 0-

4ast 254

Higher numbers correspond to higher priorities. If no priority is specified for atask, PRIORITY'FIRST is assigned during task creation.

8 Representation Clauses

Address clauses are implemented, but only for objects.

The 'SIZE length clause is implemented. %Enumeration representation clause' s are implemented.

Record representation clauses are implemented.

Interfacing to Assembly, C, and Ada is supported via pragma export andpragma interface.

Unchecked- conversion is implemented without restriction.

9 Main Programs

Main programs may have parameters and return values of discrete types or

unconstrained strings. Default values are also permitted.

B-6

V 3

-- The following software is the sole property of -- SIrvine Compiler Corporation --

containing its proprietary, confidential information.

topyright (C) 1982-1987 Irvine Compiler Corporation --

p~:~ iystem is

tyj-' lame is (m68000)

f."-uage Oefinpd Constants N

. - " lCme 5 Coti:PB:aat name m 10;4horageunil.. con.qtanJ" :- 8; -. Loragt unit i,' bits.memory_size ,constant :- 4096., L024; Bytes.min-int : constant :=-2k*31;maxint : constant := 2**31-1;maxdigits : constant =15;maxmantissa: constant := 31;finedelta : constant := 2.0**(-30);tick : constant := 1.0/60.0;

type address is range minint..max-int; -- Signed 32 bit range.subtype priority is integer range 0..254; -- 0 is default priority.

- Con. wants for the HEAPS package

bits-per-bmu : constant := 8; .. Bits per basic machine . nit.maxalignment: constant := 4; -- Maximum alignment required. iminmem_block: constant := 1024; -- Minimum chunk request size. .,.-

-- Constants for the HOST package

hostclockresolution: constant := 1; -- 1 microsecond.basedate-correction : constant := 25_202; -- Unix base date is 1/1/1970. :-

pragma put-line("Target: ", system-name);end system;

B-7 •

~(~LV .~ N,. ~~N"~ ~JJVJ\.~ P~7~A~ FA1 K.X~(~ ~U~ ~u~u v ~y ~~ ~....- ~ 2bp

%f

A P PV0

TEST ',-.,.'METERS

tests in the A;VC make use of' implementation..dependent values, 3,.Uhas the nuaximum length of an input line and invalid file names. A test thatmakes 1'.ie of' such values is identified by the extension .TST in its filename. Actual values to be substituted are represented by names that beginwith a dollar sign. A value must be substituted for each of' these namesbefore the test is run. The values used for this validation are givenbelow.

Name and Meanin -______ Value_____

$BIGLDI (1-.253 => 'A', 25~4 => '1')Tfdr-ntifier the 3ize of themaximum input line length withvarying last character.

PA .D2 (1.-253 => 'A', 25J4 => '2')Identifier the size of themaximum input line length withvarying last character.

$BIG_1D3 (1-.126 1 128..254 => 'A', 127 => '3')Identifier the size of themaximum input line length withvarying middle character.

$BIG_1DN (1-.126 1128..254 => 'A', 127 => '4') .

Identifier the size of themaximum input line length withvarying middle character.

$BIG INTLIT (1-.251 => '0', 252..254 => "298"1)An initeger literal of value 298with enough leading zeroes sothat it is the size of themaximum line length.

c-1

TEST PARAMETERS

Name and Meaning Value_ _ _

$BIG REAL LIT (1..248 => '0', 249..254 => "69.0EI")A real literal that can beeither of floating- or fixed-point type, has valie 690.0, andhas enough leading zeroes to ,bethe size if the nax1mum lintlerieth.

(1.234 -> '

A sequence of blanks twenty"racters fc,, ro than the size-. e iximuu line length.

,,.,o1' iN . AST 214(483647

A universal integer literalwhose value is TEXT_IO.COUNT'LAST.

$EXTENDED ASCII CHARS "abcdefghijklmnopqrstuvwxyzl$%?@[\]^ " {}"A string literal containing allthe ASCII characters withprintable graphics that are notin the basic 55 Ada characterset.

. [LD LAST 2147483647

A universal integer literals.hose value is TEXTIO.FIELD'LAST.

:i NAME WITH BAD CHARS /xxx/xxx/xxxAn illegal external file namethat either contains invalid 5characters, or is too long if noinvalid characters exist. .V"

$FILE NAMEWITH_WILDCARD CHAR /xxx/xxx/xxx*An external file name thateither contains a wild cardcharacter, or is too long if no 1

wild card character exists.

$GREATER THAN DURATION 524 287.5A uni'versal real value that liesbetween DURATION'BASE'LAST and 5DURATION'LAST if any, otherwiseany value in the range ofDURATION.

$GREATERTHANDURATION BASE LAST 10_000_000.0The universal real value that is -greater than DURATION'BASE'LAST,if such a value exists.

C-2

I P,

TEST PARAMETERS 0.%

Name and Meaning Value

$ILLEGAL EXTERNAL FILE NAMEI /xxx/xxx/xxxAn illegal external file name.

$ILLEGAL EXTERNAL FILE NAME2 /xxx/xxx/xx2An illegal external file namethat is differ,';:t from.. L[EGAL EX T1RNAL FIT '- !AME1.

IN CLGER FIRST -214740z648The uni ',l-sal intee:Lr literai.expressijn whose value is

INTEGER' FIRST.

$INTEGER LAST 2147483647The universal integer literalexpression whose value is

INTEGER ' LAST.

$LESS THAN DURATION -524_287.5 I.A universal real value that liesbetween DURATION'BASE'FIRST andDURATION'FIRST if any, otherwise

any value in the range offDURATION.

'i.'-S THAN DURATIONBASEFIRST -10_000_000.0

Che universal real value that i3less than DURATION'BASE'FIRST,if such a value exists.

$MAX DIGITS 15The universal integer literalwhose value is the maximumdigits supported forfloating-point types.

$MAX _IN_ LEN 254The universal integer literalwhose value is the maximuminput line length permitted bythe implementation.

$MAX INT 2147483647

The universal integer literalwhose value is SYSTEM.MAXINT. %

C

C- 3 :l

- !~

TEST PARAMETERS

Name and aning Value

$NAME TINY INTEGER SA name of a predefined numerictype other than FLOAT, INTEGER,SHORT-FLOAT, SHORT lkITEG ER,LONG FLOAT, or LONG INTEGERif one exL3tt, otherwiae any,indefined name.

Sr .i BAS1.D INT 8#3777T0 77760A base1 integer literal whosehighest order nonzero bit'alls ,.1 the sign bitposition of the re(ristntation Ifor SISTEM.MAXINT.

$NON ASCII CHAR TYPE (NONNULL)An enumerated type definitionfor a character type whoseliterals are the identifier 0NONNULL and all non-ASCIIcharacters with printable

graphics.

C-4 '

S'

a

APP: :N'OX D

WHDRAWN TESTS

I

Some tests are withdrawn from the JCVC because they do rot conform to theAda Standard. The following 19 tests had been withdrawn at the time of

validation testing for the reasons indicated. A reference of the form"AI-ddddd" is to an Ada Commentary.

. C32114A: An unterminated string literal occurs at line 62.

• B33203C: The reserved word "IS" is mri:spelled at line 45.

. C34018A: The call of function G at Lin 114 is ambiguous in thepresence of implicit conversions.

4.C35904A: The elaboration of subtype declarations SFX3 and SFX4may raise NUMERICERROR instead of CONSTRAINT ERROR as expected inthe test.

" B37401A: The object declarations at lines 126 through 13 followsubprogram bodies declared in the same declarative part.

" C41404A: The values of 'LAST and 'LENGTH are incorrect in the ifstatements from line 74 to the end of the test.

" B45116A: ARRPRIBL1 and ARRPRIBL2 are initialized with a value of a.

the wrong type--PRIBOOLTYPE instead of ARRPRIBOOL TYPE--at line41.

* C48008A: The assumption that evaluation of default initial values

occurs when an exception is raised by an allocator is incorrectaccording to AI-00397.

* B49006A: Object declarations at lines 41 and 50 are terminated !

incorrectly with colons, and end case; is missing from line 42.

B4AO10C: The object declaration in line 18 follows a subprogrambody of the same declarative part.

D- 1

WITHDRAWN TESTS

" B74101B: The begin at line 9 causes a declarative part to be

treated as a sequence of statements.

" C87B50A: The call of "/=" at line 31 requires a use clause for

package A.

• C92005A: The "/=11 -. type PACK.BIG INT at Iirue 40 is not visibl,.without a use cI ause for the packs '-- i -CK,.

,.940ACA: Thc asjumption I.hat allo.-t3d task TTI will run prior tothe main program, and t ktr .sig PYNTMB the value checked for bythe main progeam, is erroneous.

CA3005A. .D (4 tests): No valil.j .. aboratLon or'dor exists for theo'.Stests.

* BC3204C: The body of BC3204C0 is missing.

7,1

D..

'-

D-2