Revised Test suite resultsSept 5, 1981 J R GreenwoodKResults from the test of the Aug 13, 1981 Npraxis ( vax->vax) and Npraxis11 compilers. PThe suite can now handle the RSX compiler in compatibility mode. However the RSXGcompiler is very very poor, and fails on simple things. Try TEXTIO etc.LThe suite is completely upgraded. I've edited each routine again to get theMnames right and correct for packed strings etc. Also I've found a few typoswhich should be ok now.)The names of the routines are as follows:/Pxxxxx - routine that should run and print PASS=Xxxxxx - routine that should run and print PASS ( new ones )EFxxxxx - routines which generate compile-time errors. These are not even run.GRxxxxx - routines that generate run-time errors. Many times these will; print DEVIATES if the compiler didn't handle the run-time checking correctly.CA major type-checking bug is that the type of the INITIALLY item onFoptional parameters is not checked against the formal parameter type.ANearly every Xxxxxx rooutine fails. I won't bother to list them.AMany of the P00xxx routines fail. Again just run that portion tocheck them out.7About half the Rxxxx routines are incorrectly compiled.MThe following Pxxxx routines fail the tests as noted below for each compiler:JThe message in each column reflects the message printed by the routine or Kif just an "x" then it just failed. If it says "ok" then it passed on thatMcompiler but failed on the other. NOTE: there are some routines which passed1on the vax/11 compiler but failed on the vax/vax.M-----------------------------------------------------------------------------Routine VAX/VAX VAX/PDP-11 M-----------------------------------------------------------------------------P1p5d4 deviates P2p2d4 x P2p2d4T x P2p2d3 xP3d1 xP3d6 deviatesP4p3p3d5 error not detectedP4p3p3d6 " "P4p3p3d7 " "P4p3p3d8 " " P4p3p4d2 xP4p3p4D5 blows P4p5d9 blows P4p6d4 blows P4p6d6 blowsP5pp4d1 blowsP5p4d2 ( bad object ) P6p1d4 xP6p1d6 ( bad object )P6p2d4 run-time errr P6p3p1d5 x P6p3p3d1 x P6p5p3d3 x P6p5p3d4 xP6p5p3d5 error not detected P6p5p4d1 xP6p6p3d1 blowsP6p6p3d2 error not detected P7p1d2L xP7p2p2d2c failP7p2p2d3 blowsP7p2p2d3c blowsP7p2p4d2 blows P7p2p4d3 x P7p2p5d2 xP7p2p2d8 blows P8p2p2d2 failP8p3p5d4 infinte loop okP8p3p5d5 error not detectedP8p3p5d6 "" "P8p3p5d8 infinite loop okP8p3p9d10 failP8p3p910L failP8p3p9d15 failP8p3p9d20 nested too deepP8p3p9d7 bad For loopP8p3p9d7D "" """P8p3p9d7E " "P8p3p9d7C " "1F005optnl (no type checking ) ( no type checking)GThe routines ending in .KIL or .BAD are copies of various edit versionsEof the routines that either blew the compiler or failed to catch someKerrors. Each should be looked at individually. If they pass the current@compiler, then great; if not hopefully they will point a finger.