perm filename BUGS[S,AIL]20 blob sn#079613 filedate 1974-01-01 generic text, type C, neo UTF8
COMMENT ⊗   VALID 00009 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	IV-IZ AND J SERIES BUGS
C00009 00003	K-SERIES 
C00015 00004	L-SERIES BUGS
C00021 00005	M-SERIES BUGS
C00027 00006	N-SERIES BUGS
C00032 00007	O-SERIES BUGS
C00038 00008	P-SERIES BUGS
C00044 00009	Q-SERIES BUGS
C00046 ENDMK
C⊗;
IV-IZ AND J SERIES BUGS

#<NUMBER> <TAB> DESCR (INITIALS OF PERSON ENTERING BUG)
	[FILES]  INITIALS (DATE FIXED) {OK WHEN CHECKED}

#IV	DRYROTS AT NOSY -- NON-EXTERNAL PROCEDURE
	UNDECLARED FORWARD MESSAGE PROCEDURES SHOULD BE IGNORED
	[GEN/29] RHT (9-22-72) OK JRL

#IW 	IF STATEMENT INSIDE OF DO LOOP- PARSE ERROR
	[HEL]  KVL (9-22-72) OK JRL

#IX	CAUSE LOSSAGE -- BUG FIXED BUT SUSPECT FILE IS OLDER
	THAN IT SHOULD BE.  I.E. FEAR THAT SOME PREVIOUS DEBUGGING
	WAS LOST.
	[NWORLD] RHT (9-22-72) OK RHT

#IY	SPURIOUS CALL TO BEXIT IF EXTERNAL PROC DECL IN SIM PROC
	THE PROBLEM WAS KILL SET GOING OUT FOR BLOCK
	[PROCSS] RHT (9-25-72)

#IZ	GLOBAL ARRAYS IN OUTER SEGMENTS GETTING BAD LVI ENTRIES
	FIXED BY NOT PUTTING OUT LVI FOR GLOBALS
	[GEN] RHT (9-25-72)

#JA	BEGIN INTEGER I; BEGIN DEFINE I=....  -- COMPLAINS ABOUT
	DUPLICATE IDENTIFIER DECLARATION WHEN DEFINING I.  THIS
	IS DUE, POSSIBLY, TO DEFINES NOW BEING PLACED GLOBALLY EVEN
	WHEN DEFINED LOCALLY -- SHOULD BE AT LEAST DOCUMENTED, SINCE
	IT IS A DISTINCT INCOMPATIBILITY.  (DCS)

#JB	PROCEDURES INSIDE SIMPLE PROCEDURES CAUSE TROUBLE. (RHT)

#JC	REQUIRE "FOO    [PRJ,PRG]" SOURCE_FILE SEEMS TO CAUSE 
	A SAIL COMMAND ERROR (RHT)

#JD	DATUM(A←COP(B⊗C)) DOESN'T  PARSE CORRECTLY.(JRL,KVL)
	[LEAP,HEL,GEN] JRL (9-27-72) OK JRL

#JE     LNOT OF A CONSTANT NOT PREFORMED.
	[EXPRS/6] JRL (9-26-72) OK JRL

#JF	MESSAGE PROCEDURE LINK BLOCK GETTING PDA INSTEAD OF ENTRY ADDR
	[GEN/29] RHT (9-27-72)

#JG	IDPB GOING OUT AS IBP, PROBLEM WAS B GETTING CLOBBERED BY TOTAL
	[EXPRS/10] RHT (9-27-72) OK RHT

#JH	USER INITIALIZATION REQUEST LOSSAGE (HRLZI WAS IN AS HLRZI)
	[GEN/35] RHT (9-29-72) OK RHT

#JI	IFGLOBAL NOT WORKING(HAND-EYE SYSTEM)
	[LEPRUN] JRL (10-2-72)

#JJ	DRYROT ERASE1 FP2 FREE LIST WAS BEING GARBAGED
	[LEPRUN] JRL (10-2-72)

#JK	WHEN RECLAIMING  VALUE SET PARAMETER LIST SPACE, AC 1 WITH FUNCTION
	RESULT IS DESTROYED.
	[STATS] RHT (10-3-72)

#JL     THE BNDFOR BIT WAS BEING TURNED OFF FOR SETS EVEN THOUGH VALID ONLY FOR ITEMS
	(LEPRUN] JRL (10-4-72) OK JRL

#JM	SYMBOL FOR BLOCK GOING OUT WITH WRONG DDT LEVEL FIXED BY MOVING
	THE KILL SET SEMBLK PTR IN THE BLOCK SEMBLK
	[PROCSS] RHT (10-4-72) OK RHT

#JN	LENGTH(ITEM⊗ITEM) PRODUCED "ITEM TYPE MISMATCH", DUMMY SEMBLK FOR DERIVED
	SET NOT PLACED IN PROPER LOCATION.
	[LEAP] JRL (10-8-72)

#JO	COMPILER DOESN'T ACCEPT {ITMVR←ITMEXPR} BECAUSE AE NEVER BECOMES IP OR SP
	[HEL,LEAP] JRL (10-8-72)

#JP	EVALUATION OF MACRO CALL IN MACRO DEFN WASNT ALWAYS HAPPENING. RHT
	[SYM,HEL,GEN] HJS (10-12-72)

#JQ	ERROR RECOVERY PROD FOR MEMORY CALLED AT BAD TIME RHT
	[HEL/11] RHT (10-15-72) OK RHT

#JR	CODE FOR DISPLAY STRING ITEMVARS INCORRECTLY USING STRING STACK
	[TOTAL/24,9] JRL (10-17-72)

#JS	EVLLST NOT ADJUSTING ADEPTH. RHT
	[LEAP/23] RHT (10-17-72) RHT OK RHT

#JT     LIST PROCEDURES SOMETIMES RETURN FREE_STORAGE LIST AS RESULT
	[STATS] JRL 

#JU	QUICK CODE FORGETS AC1 IN A VERY BAD WAY
	[GEN/49] RHT (10-22-72) OK RHT

#JV	MEMORY[X] TRIES TO INDEX WITH AC 0
	[GEN/41] RHT (10-20-72) OK RHT

#JW	PUT ITM IN DATUM(LITMVR) AFTER ∞ DOESN'T COMPUTE ∞ CORRECTLY
	CAUSED BY HEL CALLING STSET BEFORE REFINF
	[HEL] JRL (11-2-72)

#JX	EXTERNAL PROCEDURE α, FOLLOWED IN SAME PROG. BY INTERNAL PROCEDURE α,
	IS LEGAL -- THE INTERNAL ONE PREVAILS OF COURSE -- ALLOWS INCLUSION
	OF GLOBAL EXTERNAL DECL. SOURCE FILE BY EVERYBODY, DEF'N OF PROCEDURES
	WHEREVER.
	[SYM] DCS (11-2-72) OK DCS

#JY	MEMORY[ID←XXXXX] FOULING UP ACKTAB?? RHT
	SHORT INTEGERS CAUSED THE MESS
	[GEN/42] RHT (11-2-72) 

#JZ	FROM THIS DAY FORWARD, A MACRO WILL BE ENTERED ONLY WHEN IT IS FIRST
	ENCOUNTERED.  THEREAFTER, IT WILL ONLY BE REDEFINED, AT THE SAME BLOCK
        LEVEL!! IN OTHER WORDS, SCOPE RULES ARE IGNORED AFTER FIRST APPEARANCE
	OF A MACRO, UNTIL THE BLOCK IN WHICH IT WAS FIRST DECLARED GOES AWAY.
	HOPEFULLY, LATER, A SEPARATE MACRO BLOCK STRUCTURE WILL BE INVENTED.
	[SYM] HJS (11-4-72)
K-SERIES 

#KA	REMEMBER I IN CONTEXT CAUSES PUSH P,0 TO BE EMITED
	BECAUSE SBITS ENTRY IS COPIED INTO SBITS OF ADCON
	SOLUTION DO A GENMOV(INCOR) OF PARAM.
	[LEAP] BY JRL (11-8-72)

#KAB	IT IS CLAIMED THAT IMMEDIATE INSTRUCTIONS AREN'T GENERATED
	FOR LOGICAL OPERATIONS
	OPBTS WAS A WORD SHORT AND WORD OPBTS+3 WAS INCORRECT
	[TOTAL/26] BY JRL (6-27-73)

#KB	SYNTUP CODE IN PRUP CLOBBERS LPSA BY CALL TO ZOTDIS
	& THEN TRIES TO USE IT.  THE TROUBLE ONLY SEEMS
	TO SHOW UP WHEN CREFFING.  I DON'T QUITE UNDERSTAND
	WHY, SINCE LPSA IS USED AS A CHAIN LINK THAT IS
	ALWAYS SEARCHED.  RHT
	[STATS/25] RHT (11-11-72) OK RHT

#KC	FOR HISEG, THE INITIAL PDA,,0 FIXUP WAS GOING TO
	THE LOW SEG.  DCS
	[SAIL/27] RHT (11-13-72) OK RHT

#KD	CORTMPS IN RECURSIVE PROCEDURES NOT WORKING CORRECTLY
	FOR ADRINS. RHT
	[STATS/35] RHT (11-13-72)

#KE	IBP WITH FIXARR ARG COMPLAINS  JRL 
	[EXPRS/10] JRL (11-17-72)

#KF	THE SYNTAX ERROR  FOR J←1 UNTIL N ... CAUSES
	A DRYROT AT GETAD.  THE TROUBLE IS THAT WAIT
	GETS ENTERED WITH THE STEP NOT SET UP 
	[STATS]

#KG	SPROUT'S ALLSTO FAILS TO CLEAR DISPLAY ON PAGE 9 OF
	TOOLS.SAI[H,AJT].  IN FACT THERE WAS NO ALLSTO IN THE CODE.
	[PROCSS] RHT (11-21-72) OK RHT

#KH	REMNENTS OF OLD FORMFX STUFF CAUSED LOSSAGE WHEN
	RELEASING VALUE SET TO SIMPLE PROC.  FIX WAS TO FLUSH IT.
	[TOTAL/27] RHT (11-21-72)

#KI	DPB USING WRONG AC IN DEPOSIT, PROBLEM WAS BAD FIX TO BUG KE
	[EXPRS/10] JRL (11-21-72)

#KJ	ECHK WITH ITEMVAR WAS RETURNING BAD TBITS IN TEMP SEMBLK
	A HRRI SHOULD HAVE BEEN A MOVEI
	[LEAP] JRL (11-21-72)

#KK	ISTRIPLE CAUSES DRYROT AT BPOP MSG. CAUSED BY GLBSTK NOT HAVING
	BEEN CALLED

#KL	STACSV SAVES 16 REGISTERS IN 14 WORDS( A REMARKABLE ACHIEVEMENT)
	[GOGOL/9] JRL(11-22-72)

#KM	POLISH FIXUP FOR EXT PD MESSED UP
	[GEN/30] RHT (11-24-72)

#KN	LPTYPCK RETURNS WRONG TOKEN TYPE. TLNN SHOULD HAVE BEEN TLNE
	[LEAP] JRL(11-26-72)

#KO	CVLIST DOES NOT CORRECTLY MARK RESULT AS LIST
	[LEAP] JRL(11-27-72)

#KP	FDONS SOMETIMES DESTROYS AC 1. BAD THING IF A RETURN()
	[LEPRUN] JRL (11-28-72)

#KQ	STORA GETS CONFUSED BY FIXARRS INAC
	[TOTAL] JRL (11-30-72)

#KR	DATUM(ITVARR[EXPR],REAL ARRAY)[1] IN A KKP PROGRAM CAUSED A
	BAD STRING TO BE ENTERED FOR THE ARRAY NAME IN THE ARERR UUO
	FOR THE BOUNDS CHECK ON [1].  THE REASON IS THAT THE SEMBLK
	REPRESENTING THE RESULTANT REAL ARRAY DIDN'T HAVE A LEGITIMATE
	ITEMVAR SEMBLK POINTER IN $VAL, SINCE IT'S SO COMPLICATED.  
	MAYBE IT SHOULD HAVE, BUT FOR THE PRESENT, I'VE INSERTED A
	PATCH TO USE A DUMMY NAME FOR THESE GUYS
	[ARRAY] DCS (12-6-72)

#KS	ADD LOADVR SWITCH TO TAKE CARE OF DIFFERENT CODES FOR .REL,LIB
	REQUESTS FROM SAIL PROGS FOR LOADER 54.
	[SAIL,TOTAL] JRL (12-13-72)

#KT	BEXIT NOT GETTING CALLED IF ONLY HAVE KILL SET.  TYPO THE CAUSE
	[GEN/14] RHT (1-9-72)

#KU	ARRAY ITEMS SHOULD NOT NORMALLY BE OWN OTHERWISE TWO
	PROGRAMS WITH THE SAME ARRAY ITEM WILL HAVE TWO ARRAYS ALLOCATED
	[ARRAY] JRL(1-8-73)

#KV	TEST FOR INILNK = 0 FOR LIBRARY IN USER INITIALIZATION .UINIT
	[GOGOL] JRL(1-8-73)

#KW	DON'T ALLOW INTERNAL OR EXTERNAL ITEM DECLARATIONS
	[GEN] JRL (1-8-73)

#KX	AN ALLSTO SHOULD BE DONE EITHER AT BEGINNING OF BLOCK OR
	BEFORE EVERY CALL TO BEXIT
	[GEN/14] RHT (1-9-72)

#KY	IT IS CLAIMED THAT DONE OFTEN CAUSES A JUMP TO A JUMP AND THAT
	IN A SERIES OF SEVERAL DONES EACH MAY JUMP TO THE NEXT.

#KZ	DATUM OF OWN ARRAY ELEMENT DOESN'T WORK CORRECTLY, OWN BIT
	SHOULD BE REMOVED BY PREVIOUS OPERATION
	[LEAP] JRL (1-9-73)

L-SERIES BUGS

#LA	CVSIX IS DISHONEST FOR [ ] , .  
	REWROTE THE ROUTINE.
	[STRSER] RHT 11-25-73

#LB	"TYPO" IN RESUME REWRITE.  THE TARGET OF THE RESUME IS RESTARTED,
	(IN SOME "NOTNOW" CASES); NOT ONLY IS THIS NOT DESIRED, BUT ALSO
	THE STACKS AREN'T SWITCHED -- CONFUSION RESULTS.
	DCS [NWORLD] OK 1-15-73

#LC     A FORMAL PARAMETER TO A MACRO DEFINITION, WHICH HAS PREVIOUSLY
	BEEN DEFINED TO BE A MACRO NAME ITSELF DOESN'T WORK.
	E. G. DEFINE FOO(P) = ⊂...⊃; WHERE P WAS PREVIOUSLY DEFINED AS MACRO.
	[SYM] HJS 1-17-73

#LD	WHILE ITEM⊗ITEMVAR ≠ PHI CAUSES RETRIEVAL CONSTRUCTION FAILURE.
	SEE FILE BUG.SAI
	[HEL] JRL 1-22-73

#LE	SEARCHES WITH SAME ? ITEMVAR TWICE DON'T WORK
	E.G  ∀ ? X | X⊗X≡A DO
	[LEAP] JRL

#LF	ITEMVAR COMPARISONS DON'T WORK WHEN 1 THING ON STACK.
	A HRL WAS A HRLI BY MISTAKE
	[LEAP] JRL 2-4-73

#LG	RESULT OF MATCHING PROCEDURE NOT RETURNED CORRECTLY.

#LH	ASSIGN IS NASTILY FAILING TO ADJUST ADEPTH
	[LEAP] RHT 2-6-73

#LI	<INTEGER>←<REAL CON>*<INTEGER PARAM> CAUSES FAILURE TO
	TO TYPE CONVERSIONS. CAUSED BY MACRO LOSSAGE
	SUBSEQUENTLY FIXED??

#LJ	MAKE A⊗B≡FOO(ITEM) FAILS BECAUSE RDYCAL DOES NOT DO OKSTACK.
	[STATS] JRL 2-9-73

#LK	END OF MATCHING PROCEDURE CAUSES DRYROT BPOP
	[STATS] JRL 2-12-73

#LL	MATCHING PROCEDURE DOES NOT UNPROTECT AC CONTAINING UNBOUND
	[STATS] JRL 2-14-73

#LM 	PITBND NOT BINDING THE ENVIRON WHEN IT SHOULD
	[IOSER/39] RHT 2-17-73

#LN	ABORT EXECUTION AFTER FINDING A SYNTAX ERROR. ALSO MAKE SEMANTIC
	ERRORS AFTER SYNTAX ERRORS VISIBLE.
	[GOGOL/24] [GEN/26?] [SAIL/26]  KVL 2-22-72

#LO	GLOBAL ARRAY ITEMVAR ARRAYS DON'T WORK
	[ARRAY] JRL 2-23-73

#LP	GO TO OUT OF A PROCESS WAS LOOPING. PUT IN ERROR TRAP
	[IOSER/37] RHT 2-25-73

#LQ	SPROUT OU A FORWARD PROCEDURE LOSES BECAUSE PDA GETS PUT OUT
	AS 0.  EVIDENTLY, THE PD FIXUPS ARE LOST WHEN THE PROCEDURE
	IS FINALLY DECLARED. -- RHT
	[STATS] RHT 3-13-72 OK RHT

#LR	SPROUT OF AN EXTERNAL PROCEDURE LOSES BECAUSE OF SOME TROUBLE
	WITH FINDING THE PROPER KILL SET. SEE FILPRO[S,RHT]
	[PROCSS/5] RHT 3-13-72

#LS	"SAIL IN LEVEL TROUBLE" WHEN REDECLARING A VARIABLE WHICH
	HAS BEEN DECLARED IN A GLOBAL PROCEDURE -- SE TEST1.SAI[1,RKN]
	ALSO GET SIMILAR LOSSAGE IN A MACRO DECLARATION. THE TROUBLE
	WAS THAT THE LEVEL FIELDS WERE SET WRONG FOR OWN ARRAYS
	[SYM/29] RHT 3-12-73

#LT	SOURCE FILE NOT FOUND- ERRMSG PICKED UP FILENAME FROM WRONG LOC
	[SAIL/  ] JRL 3-15-73

#LU	GLOBAL NOT WORKING CAUSED BY BUG IN ALLGLO
	[LEAP] JRL 3-16-73

#LV	Lynn Quam complains that certain routines (e.g. REALIN) cause
	phoney overflows which wreak havoc with interrupt processing.

#LW	LOOP BUG.  EVIDENTLY A FORSTO (OR WHATEVER) ISN'T HAPPENING
	JUST BEFORE THE STEP UNTIL PART OF A LOOP HEADER.  THIS CAUSES
	THE COMPILER TO THING THAT DISPLAYS ARE STILL VALID AT THE
	JUMPBACK POINT.  -- SEE LOOPBG.SAI[S,AIL] FOR EXAMPLE
	FIXED BY MAKING FORSTO STRONGER.
	[#MU#]

#LX	GET A DRYROT AT GETAD FROM DRYROT.SAI[S,AIL].(COPIED FROM FAKE.SAI
	[H,TOB].  THE TROUBLE HAS TO DO WITH RANDOM DECLARED AS EXTERN PROC
	& NOT EXTERN REAL PROC.

#LY	GLOBAL PROPS DESTROYED ON PROGRAM INITIALIZATION OF ITEM TYPE.
	FIX IS TO CHECK IF THIS PROGRAM IS INITIALIZING GLOBAL MODEL.
	[LEPRUN] JRL 4-5-73

#LZ	JEG IS COMPLAINING ABOUT A DRYROT AT EFORM FROM AESTH.SAI[A,JEG]
M-SERIES BUGS

#MA	EQU("CONST",I) →→ PUSH SP,SCT1↔PUSH SP,STC2↔PUSH P,I↔
	PUSHJ	P,EQU↔  I.E. IT LEAVES OUT A CALL TO PUTCH

#MB	MACRO TYPE STRING SEMBLKS WERE BEING FREBLK'ED WITHOUT
	REMOVING THEM FROM HASH TABLE,STRING RINGS

	ALSO STRING CONSTANTS WILL NOW BE REMOPPED IF NOT IN USE
	($ADDR NON ZERO, OR KPSTR BIT ON IN $SBITS IF IN USE).
	THIS SHOULD REMEDY THE OLD STRING CONSTANT COMMENT PROBLEM
	WITH PNAMES, BLOCKNAMES AND PRELOADED STRING ARRAYS

#MC     FREBLK ING A SEMBLK (PROC ARG) WITHOUT URGSTR
	[GEN] RHT 4-20-73

#MD	PTRAC'S SHOULD BE STORA'D BY STORING ONLY RIGHT HALF, TO BE
	CONSISTENT [TOTAL] JRL 4-22-73

#ME	FORWARD MATCHING PROCEDURES CAUSE DRYROT. WAS PUTTING OUT
	CODE FOR THEM ERRONEOUSLY
	[STATS] 4-25-73

#MF	I BLEW IT IN CREFSYM, WHEN I MADE USE OF AN ALREADY EXISTENT
	ROUTINE, FRNP1, TO PRINT OCTAL SYMBOL SYNONYMS.  ANYHOW, I
	MANAGED THEREBY TO CLOBBER AC B, WHICH CAUSED THE LISTING
	FILE TO BE GARBAGED UTTERLY.  THE FUNNY THING IS THAT NOBODY'S
	COMPLAINED MUCH.
	[SYM] 5-1-73 DCS

#MG	I BLEW IT IN USING LDYFLG TO PREVENT ZEROING OF OWN ARRAYS.
	I FIXED THIS BY MAKING THE USE OF LDYFLG MORE CLEVER.
	[ARRAY] 5-10-73 RHT OK RHT

#MH	LOOP CODE GETTING DRYROT AT EPNT BECAUSE NOT BEING SURE TO
	GET ACCESS TO LOOP INCR BEFORE ADDING
	[STATS]/9 5-11-73 RHT OK RHT

#MI	LDYFLG NOT GETTING CLEARED FOR NON PRELOADED ARRAYS
	[ARRAY]/10 5-14-73 RHT

#MJ	UNTIL EXPR IN FOR STATEMENT BEING REMOPED INCORRECTLY
	[STATS]    5-15-73 JRL

#MK	EXIF2 NOT SETTING UP PROPERLY FOR CALL OF MARK WITH STRING ARGUMENT
	[EXPRS]	   5-15-73 JRL

#ML	DRYROT TMPALL CAUSED BY STACK ERRONEOUSLY RESTORING SBITS(INUSE ETC)
	[TOTAL]    5-21-73 JRL

#MM	USER NOT BEING LOADED IN EXPO VERSION OF OUTSTR
	[IOSER]	   5-26-73 JRL

#MN	GET DOES ACCESS FOLLOWED USUALLY FOLLOWED BY A GETAC WHICH CAN DESTROY
	THE DISTMP ACCESS FOUND. PATCHED THE SYSTEM COMPILER BY FOLLOWING
	THE GETAC BY ANOTHER ACCESS. HAVE NO REAL CONFIDENCE IN THIS FIX
	SO HAVE NOT CHANGED THE SOURCE
	[TOTAL] 7-13-73 RHT

#MO	ANOTHER LDYFLG PROBLEM WITH OWN ARRAYS. A SKIPN SHOULD HAVE BEEN A SKIPL
	[ARRAY]/8 5-31-73 JRL

#MP	ANOTHER STRING GARBAGE COLLECTOR BUG.  AT ENDSTR IN SYM, A CHECK IS MADE
	FOR FALSE PART OF CONDITIONAL, AND SOME CODE IS SKIPPED (ENTERS CODE)
	IF THAT IS SO.  ALSO SKIPPED IS A CALL TO UPDCNT WHICH KEEPS REMCHR
	HONEST!!!!  FIXED IT, HERE AND AT CMU, WHERE IT WAS CAUSING A PROBLEM.
	[SYM]@ENDSTR  6-1-73 DCS

#MQ	LISTING BUG IN SCANNER WHEN LPNT BACKED UP OVER MACRO NAME. SOMETIMES
	TEMPORARY IN WHICH LPNT WAS SAVED(SBITS2) WAS NOT BEING SET UP.
	[SYM] 6-9-73

#MR	NEWART IN COMPILER GOT CONFUSED WITH STRING ARRAYS, THOUGHT THEY WERE
	STRINGS.
	[LEAP] JRL 6-15-73

#MS	LET WHEN RIGHT SIDE A PARSER TRIGGERER, NOT COPYING TRIGGER BIT

#MT	IF CTVAR1 ∧ CTVAR2 THEN ... DOESNT CHECK SECOND CTVAR   RHT
	COMPILE TIME EVALUATION OF CONSTANT EXPRESSION

#MU	FORSTO WASN'T STORING ENOUGH (WE THINK) RHT
	[TOTAL] RHT 6-25-73

#MV	NEEDED AN ACCESS BEFORE A PUT IN LOOP CODE
	[STATS] RHT 6-27-73

#MW	PPMAX NOT EXTERNALED IN SAILUP (EXPORT ONLY)
	[GOGOL] JRL 6-28-73

#MX	SIMPLE PROC GIVES WARNING IF NON-SIMPLE PROCEDURE INSIDE
	[STATS/20] RHT 6-28-73

#MY	GO TO OUT OF SIMPLE PROC INTO ANOTHER SIMPLE PROOC LOSES
	[SYM/30,STATS/14] RHT 6-28-73

#MZ	ERRONEOUS ERROR MESSAGE FOR REAL CONST TO NEG INTEGER POWER
	[EXPRS/7] JRL 6-29-73
N-SERIES BUGS

#NA	IF GET AN INTERRUPT IN SCHEDULER LOOP AFTER INTENS
	CHECK BUT BEFORE DO IWAIT, YOU WILL LOSE !
	HAVE A QUASI-FIX THAT SHOULD WORK EXCEPT IF YOU
	ARE USING THE INTERRUPT MASK UUOS.  REALLY NEEDS A
	CLEAR MASK & TELL ME WHAT IT WAS TYPE THING
	[NWORLD/11] RHT 7-14-73

#NB	USER SPECIFIED CAUSE PROCEDURES WERE LOSING GROSSLY
	SETIP & SETCP WERE NOT LIKE DOCUMENTATION.
	INTERROGATE TRIED TO FIND CONTEXT WHEN NONE WAS SPECIF.
	[NWORLD,HEL,PROCSS] RHT 4-15-73

#NC	ASKNTC DID A PUSHJ WHERE A JSP WAS CALLED FOR
	[NWORLD] RHT 7-15-73

#ND     ARRAY TEMP CONFUSION WHEN DELETING LIST ARRAY ITEM
	[LEPRUN/26] JRL 7-22-73

#NE	DEFINE BIT=1 LSH 35; I←BIT; ... SETS I TO ZERO
	SIMILARLY FOR BIT='400000000000.  SEE FOO.SAI[S,RHT]
	I ← 1 LSH 35 WORKS. SEE BUG PG

#NF	FOUND A USE OF TBITS IN STKUWD
	[ARYSER] RHT 7-24-73

#NG	STKUWD LOSES WHEN GO TO OUT OF SIMPLE INTO ITS (NON-SIMPLE)
	PARENT.  FIX WAS TO ADJUST STACKS BEFORE DO LVI STUFF.
	[ARYSER] RHT 7-24-73

#NH	DEFAULT PARAMS WEREN'T DOING RIGHT BY ADEPTH
	[STATS] RHT 7-25-73

#NI	FIXUP FOR CONTINUE WITHING DO UNTIL LOOP NOT CORRECT
	[STATS] RHT 7-29-73

#NJ     TEMP FOR EXPRESSION ARGUMENT TO FORTRAN CALL BEING REMOPPED
        TOO EARLY BY FTRARG (WHEN CALLED FROM RECURSIVE PROCEDURE)
        SIMILAR PROBLEM WHEN SAIL USES A TEMP FOR RESULT OF EXPRESSION
	BEING PASSED TO A REFERENCE PARAMETER OF PROCEDURE WHEN
	TEMP IS RECURSIVE.

#NK     TEMPS SHOULD NOT HAVE DISPLAY LEVEL.
	[TOTAL/16,/20] JRL 8-2-73

#NL	BOOLEAN A⊗ANY≡ANY ALWAYS FAILS.
	[LEPRUN] JRL 8-4-73

#NM	RELATIONS INVOLVING BINDING ITEMVARS CAN'T BE DONE WITH MEMORY;
	[LEAP] JRL 8-5-73

#NN	0.0↑.5 CAUSES EXPONENTIATION UNDERFLOW ERROR MESSAGE
	[GOGOL] JRL 8-6-73

#NO	GIVE ERROR MESSAGE FOR EXTRA ENDC,ELSEC'S
	[SAIL] HJS 8-6-73

#NP	COMPILER COMPLAINS WHEN MATCHING PROCEDURE CONTAINS NO 
	? PARAMTERS (DRYROT:BPOP)
	[STATS] JRL 8-12-73

#NQ	FIX UP TO STRING ITEMVAR ADCON NOT GOING OUT CORRECTLY
	SAME OLD PROBLEM (STRING ITEMVAR WAS TREATED AS STRING).
	[GEN/29] JRL 8-12-73

#NR	NEW("STRING CONSTANT") CAUSES A DRYROT.  
	SAME OLD PROBLEM, REMOP BEING CALLED TWICE.
	[LEAP/21] JRL 8-13-73

#NS	LPINI SOMETIMES GETS A DRYROT-EXPAND CODE. 
	CAUSED BY HLRZ WHICH SHOULD HAVE BEEN HLRE
	[LEPRUN/6] JRL 8-16-73

#NT	ALLSTO IN BLOCK WITH PROCEDURE DECLARATION CAN CAUSE TEMP
	TO GO WITH PROCEDURE'S TEMP RING. 
	[STATS/20] RHT 8-19-73

#NU	TRAGO FOR CONTINUE IS LOSING FOR WANT OF A TEST FOR KILL SETS
	[STATS/15] RHT 8-19-73

#NV	EXPONENTIATION CNST↑CNST WAS NOT MARKED AS CNST
	[EXPRS/7] RHT 8-19-73

#NW	DRYROT WHEN DELETING STRING ARRAY ITEM
	[LEPRUN/31] JRL 8-26-73

#NX	DATUM(BINDINGIV,TYPE) DOESN'T WORK BECAUSE MPBIND BIT IS OVERWRITTEN;
	[LEAP/14] JRL 8-30-73

#NY	PROFILE DID NOT KNOW ABOUT MATCHING PROCEDURES.
	[PROFILE.SAI/12] JRL 8-30-73

#NZ	DELETE OF BINDIT & FRIENDS SHOULD CAUSE AN ERROR MESSAGE
	[LEPRUN/27] RHT 8-30-73
O-SERIES BUGS

#OA	REMOVE ALL ITEM SCREWS UP FREE STORAGE WHEN IT REMOVES ONLY ITEM
	FROM LIST
	[LEPRUN] JRL 9-4-73

#OB	SPROUT_DEFAULTS CAUSES FUNYNESS WHEN IT IS THE FIRST DECLARATION
	IN A PROCEDURE. MORE ON THIS: SPROUT_OPTIONS IS ALL QUITE HAPPY
	IF YOU GIVE IT A LITERAL OCTAL NUMBER, SAY '1400, ALL IS FINE.
	IF INSTEAD YOU SAY PSTACK(3), THE NEXT DECLARATION SOMEHOW
	DOESN'T TAKE.  SEE BUG.SAI[THE,RHT].  THE PROBLEM ALSO OCCURS
	IF YOU USE A CONSTANT EXPRESSION LIKE (3 LSH 8).
	PROBLEM WAS THAT SDFFLTS WASNT CLEARING BITS. 
	[GEN/37] RHT 10-31-73

#OC	PROFIL DID NOT KNOW ABOUT CONTINUE STATEMENTS. IT DOES NOW.
	[PROFIL.SAI] JRL 9-9-73

#OD	TYPE BITS NOT BEING SENT TO  ARRAY ITEM ALLOCATOR
	[ARRAY/8] JRL 9-14-73

#OE	DRYROT AT CORREL WHEN DELETING DECLARED STRING ARRAY ITEM
	[LEPRUN/31] JRL 9-15-73

#OF	CREF BUG, CAUSED BY NOT RELOADING AC A WHEN SCANNING FALSE PART
	OF IFCR EXPRESSION
	[SYM/9] HJS 9-17-73

#OG	STRING GARBAGE COLLECT BUG, COUNT OF PNAME WASN'T BEING SAVED
	[SYM/23] HJS 9-19-73

#OH	CREF BUG: GARBAGE FOR MACRO FORMALS
	SOLUTION: IGNORE THE LITTLE CRITTERS
	[SYM/30] HJS 9-24-73

#OI	INTERESTING BUG ENCOUNTERED WHEN TESTING AUTO DECLARATION OF
	UNDECLARED VARS: GET A "STORA A THING NOT IN AC" IN FILE
	ACBUG.SAI -- RHT,KVL

#OJ	FAILED TO TO A GETBLK FOR A SPROUT APPLY.  FIX WAS IN SAPPL1.
	[LEAP/28] RHT 10-14-73

#OK	REF_ITEM(ITEMX) WAS LOSING
	[LEAP/21] RHT 10-14-73

#OL	TYPO IN APPLY
	[ARYSER/7] RHT 10-14-73

#OM	TYPO IN LEAP
	[LEAP/28] RHT 10-14-73

#ON	BUG IN STKCHK FOR LEAP FOR ? LOCALS
	E.G. ∀ ? X | X ε {{A,B}} DO ... LOSES
	[LEAP/9] JRL 10-14-73

#OO	SPROUT APPLY NOT SETTING UP SPRPDA IN STATL
	[NWORLD/7] RHT 10-14-73

#OP	A WASNT GETTING SAVED BY APPLY
	[ARYSER/8] RHT 10-14-73

#OQ	MAKE ITM⊗LOP(A)≡LOP(B) GIVES RETRIEVAL-CONSTRUCTION FAILURE
	[LEAP/18] JRL 10-19-73

#OR	ANOTHER STRING ITEMVAR IS NOT A STRING BUG.
	[TOTAL/13] JRL 10-26-73

#OS	GETTING AN ILL MEM REF IN THE COMPILERCAUSED BY STCAT BEING 
	CALLED WITH GENLEF=0, AS HAPPENS WHEN DO A CVMS(UNDEC). RHT
	SEE STCBUG.SAI[S,AIL] HJS 10-31-73 

#OT	SPROUT APPLY WAS TRYING TO LOOK UP STACK FOR STATIC LINK EVEN 
	WHEN ONE WAS SUPPLIED IN THE PROCEDURE ITEM.  THIS IS A
	CLEAR LOSS, SINCE YOU MAY HAVE TO LOOK FOREVER.
	[NWORLD/7] RHT 10-30-73

#OU	SPROUT APPLY DEFAULTS CODE HAD A TYPO (THERE SEEM TO BE A LOT OF EM)
	[NWORLD/7] RHT 10-30-73

#OV	SEEMINGLY, THERE IS A BUG WITH THE ALLCON STUFF IN EXPRS.
	AS NEARLY AS I CAN TELL, IF A CONSTANT SEMBLK IS MARKED
	INAC, THEN ARITH WILL NOT TRY TO EVALUATE BOTH PARTS.
	SEVERAL QUESTIONS ARISE AS TO WHY A CONSTANT SEMBLK MARKED
	INAC OR OTHERWISE WAS SITTING AROUND AT ALL, BEYOND WHEN
	IT MAY BE USEFUL, BUT ... 
	SEE EXPRS AT THE BOTTOM OF P. 4-1  RHT

#OW	BUG IN CALCULATION OF FOREACH ITEMVAR LOCAL ADDRESS WHEN LOCAL REQUIRES
	UP LEVEL ADDRESSING. A MOVE SHOULD HAVE BEEN A HRRZ
	[LEPRUN/15] JRL 11-4-73

#OX	ITV ↔ ITV2 DOESN'T WORK IF EITHER IS A ? PARAMETER.
	[EXPRS,TOTAL] JRL 11-4-73

#OY	MAKE NOT TESTING TO MAKE SURE ALL THREE ARGUMENTS ARE ITEMS
	[LEAP/16] JRL 11-4-73

#OZ	GET INSIST OF ITEMVAR DOESN'T WORK IF TYPE BITS ARE ON
	[TOTAL/11] JRL 11-13-73
P-SERIES BUGS

#PA	GENMOV(GET,ADDR) OF MPPARM (? ITEMVAR) WAS DESTROYING AC 3
	[TOTAL/14] JRL 11-13-73


#PB	APPLY SEEMS TO BE FORGETTING TO DO AN ALLSTO.
	[LEAP/28] RHT 11-15-73


#PC	FIRST LINE OF CREF OVERWRITTEN.  
	[SYM/8,SYM/22] HJS 11-16-73 

#PD	STACK GETS OUT OF HAND WHEN HAVE CONDITIONAL LEAP EXPRESSION
	PROBABLY ALSO IF CASE EXPRESSION
	[HEL/8,LEAP/22] JRL 11-24-73

#PE	PRELOADING TWO STRING ARRAYS IS A LOSER.  THE REASON WAS THAT
	THE PRELOAD CODE WAS RATHER CARELESS WITH ITS COUNT VARIABLE
	LDYTOT.
	[ARRAY/11] RHT 11-25-73

#PF	FILE ENDING IN FF BLOWS UP COMPILER.
	[SYM/22] RLS 11-27-73

#PG	CVS BARFS ON LARGEST NEGATIVE NUMBER (YIELDS - 0)
	[STRSER/15] RLS 11-28-73

#PH	BOOLEAN CODE IN FOREACH DOESN'T WORK WITH REENTRANT COMPILATIONS(/H)
	FIXUP WAS BEING ERRONEOUSLY SUPPRESSED.
	[LEAP/12] JRL 11-29-73

*PI	TURN OFF MACRO EXPANSION WHILE SCANNING FORC OR FORLC LOOP VARIABLE.  
	[HEL/16] HJS 11-30-73 

#PJ	NOMAC WAS LOSING ITS ARGUMENT SINCE IT WAS BEING POPPED FROM THE STACK.  
	[HEL/17] HJS 11-30-73  

#PK	ACCESS CONSTRUCT IN START CODE MEANS THAT OUGHT TO DO A REMOP
	AFTER EMIT INSTRUCTION.
	[GEN/57]  RHT 12-2-73

#PL 	ARRBLT WAS BLTTING IF LENGTH LEQ 0.  IF LENGTH NEGATIVE, THIS
	CAUSED A WRAP AROUND.
	[ARYSER/5]  RLS 12-1-73

#PM	INPUT LOST A CHAR WHEN AN SOS FILE ENDED WITH A LINENO WITH
	THE TAB IN THE NEXT BUFFER.  COMMON WHEN FILE IS ON 10-STYLE 
	DECTAPE (SINCE '177 WORDS PER BUFFER).
	[IOSER/14]  RLS 12-1-73

#PN	ADD A RESET AT VERY START OF SAIL.
	[SAIL/28] RHT & JRL 12-5-73

#PO	PTY CODE WAS MANGLING 12 (DID PTYUUO 5,CDB)
	FIXED BY USING ACS C & D.  ALSO, LOOKED TO SEE THAT THEY
	WERE OK. THEY SEEMED TO BE (ONLY USE OF C GOT REPLACED BY T)
	[IOSER/34] RHT 12-5-73

#PP	REFERING TO BUILT-IN ARRAYS WHICH HAVE "NEGATIVE"
	VIRTUAL ORIGINS, WAS A LOSER WITHIN HISEG COMPILATIONS. THIS 
	CAUSED BY WAY LOADER DECIDES
	WHICH OF THE TWO RELOCATION FACTORS TO USE.
	FIX FOR NOW IS TO SIMPLY GIVE ERROR MESSAGE IF THIS HAPPENS.
	[ARRAY/15] JRL 12-5-73

#PQ	SPRPD WANST SETTING UP FOR CALL TO LODPDA
	[PROCSS/3] RHT 12-6-73

#PR	COMSER ERR HANDLER SNARFING A CR & LEAVING THE LF HANGING
	AROUND.  THIS IS NOT GOOD.
	[COMSER]  RHT 12-6-73

#PS	CALLING ERROR HANDLER DURING COMMAND SCANNER (COMPILER), BARFS
	IF REPLIED TO BY "S"
	[SAIL]	JRL 12-7-73

#PT	RELATIONS BETWEEN ITEMEXPRS AND ARITH EXPRESSIONS NOT ALWAYS 
	FLAGGED AS ERRORS.
	[EXPRS/ ] JRL 12-9-73

#PU	ERROR MESSAGES AT RUNTIME WERE ACTING AS IF AN ERRONEOUS
	RESPONSE CHAR HAD BEEN TYPED.
	[GOGOL /26] RFS 12/10/73

#PV	ATAN REMOVED TOO MANY THINGS FROM STACK WHEN GIVEN A SMALL ANGLE
	[TRIGS/7/8 ] JRL 12/11/73

#PW	TRIG FLOT OV HANDLER ALSO NEEDED TO ENABLE FOR REGULAR OVERFLOW,
	SINCE DEC SETS SEVERAL BITS.
	[TRIGS/3] RHT 12/12/73

#PX	ADD MORE ERROR CHECKING (FOR POTENTIAL DRYROTS) IN LEAP STACK MANIPULATIONS
	[HEL,LEAP] JRL 12-12-73

#PY	NOMAC WAS LOSING BECAUSE WHEN IT CAME BACK IT DID AN EXTRA SCAN
	FIX WAS TO BACK UP SCANNER (SCNBAK) ONE BEFORE RETURNING
	[HEL] JRL 12-12-73

#PZ	DCS DISCOVERED LOSSAGE IN DEFCHK. ESSENTIALLY, STRINGC HAPPENING
	AT A TIME IT DIDN'T USED TO.  THE FIX ACTUALLY DOCUMENTS THE BUG.
	[SYM/14] RHT 12-14-73

Q-SERIES BUGS

#QA	PARAMS NOT RIGHT TO GC TRAPS IN GOGOL
	[GOGOL/44] RHT 12-14-73

#QB	CVG WASN'T DOING LARGEST NEG RIGHT
	[STRSER] RFS 12-14-73

#QC	END OF FILE NOT DETECTED CORRECTLY FOR TTY INPUT TO REALIN.
	THE EFFECT WAS THAT YOU WOULD READ INFINITE NUMBER OF ZEROES
	FROM THE FILE, NEVER SETTING EOF.
	[IOSER] RFS 12-15-73

#QD	BUG IN NUMIN SNARFS A + OR - SIGN FOLLOWING A LEGAL NUMBER.
	THIS IS A BUG (I.E. NUMIN DOES NOT FOLLOW THE SYNTAX DOCUMENTED
	FOR IT IN IOSER).
	[IOSER] RFS 12-15-73
#QE	LDE reported CAT bug when used with new STRNGC:  if CAT decides
   that first arg. need not be copied, but then has to to STRNGC
   to get room for second arg, and STRNGC adds new space, it is no logner
   true that the first arg needn't be moved.  My fix is, whenever
   a garbage collect must be done in this instance,both strings are
   moved, need it or not.
   [STRSER] p. 4 12-30-73 DCS

#QF	Same bug as QE, only this time in SYM in the compiler. The same
   old formals to macro body problem -- if GC forms new block, the
   correspondences between topbyte and string will not be maintained. Same
   thing, in fact, if ID-scanning is interrupted by such a GC.  I don't
   have a fix yet.
   [SYM] DCS (eventually)