Number: 291

Date: 26-Mar-84 13':20':40

Submitter: Sannella.PA

Source: Masinter.pa

Subject: Output of 1st pass compiler illegible

Assigned To: Masinter.pa

Attn: 

Status: Closed

In/By: 

Problem Type: Design - UI

Impact: Annoying

Difficulty: 

Frequency: Everytime

Priority: Perhaps

System: Language Support

Subsystem: Compiler, Code Format

Machine: 1132

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: [lmm 27 mar': changed to Language/Compiler. Went to mark as fixed and fount it already fixed]'
["Sannella" "20-Aug-84 18':17':07" Attn': Status':(Fixed->Closed)]

Description: '
Date': 23 Mar 84 18':32 PST'
From': Masinter.pa'
Subject': output of 1st pass compiler smashed somehow'
To': lispsupport'
'
if you do LISTING T in the compiler, the output of the first pass is much less legible than it used to be. Dunno what happened. Maybe something got lost last edit of BYTECOMPILER?'
'
-----'
'
Date': 26 Mar 84 18':12 PST'
From': masinter.pa'
Subject': Lisp': fixed problem with first pass output from BYTECOMPILER'
To': LispSupport.pa'
cc': Kaplan.pa'
Lisp-System-Date': 26-Mar-84 11':03':55'
Machine-Type': Dorado'
'
Somewhere in the course of Ron''s edit to the hasharray creation call, some properties in the bytecompiler got messed up; what used to have'
'
(PUTPROPS FN MLSYM (%[ %] FN))'
'
turned into'
(PUTPROPS FN MLSYM (NIL FN))'
'
I don''t know how or why this happened, which is a separate (mysterious) AR.'
'
Ron, do you have any idea how this got smashed, i.e., were you manipulating the file with any odd mechanisms?'
'
-----'
'
Date': 27 Mar 84 14':30 PST'
From': Masinter.pa'
Subject': bytecompiler blues'
To': LispCore^'
cc': LispFriends^'
'
Edit got dropped and BYTECOMPILER in this mornings <LispCore>Next> sysouts still have call to NOT^H instead of NOT. '
'
Fixed in next loadup. Workaround for u.d.f. NOT^H is to MOVD(NOT NOT^V^H).'
'
-----'
From': kaplan.pa'
Date': 30-Mar-84 23':10':40 PST'
Subject': Re': Lisp': fixed problem with first pass output from BYTECOMPILER'
In-reply-to': masinter''s message of 26 Mar 84 18':12 PST'
To': masinter'
cc': LispSupport, Kaplan'
'
My edit was a perfectly vanilla EDITCALLERS-MAKEFILE.  I have no idea how that could have gotten messed up--unless a previous file in the EDITCALLERS clobbered the FILERDTBL in some way.  Hard to believe, but if there is a clobbering expression for FILERDTBL somewhere, we''d better find it and make sure that it is an INITVARS or the equivalent.'
'
--Ron'
'


Workaround: 

Test Case: 

Edit-By: Sannella

Edit-Date: 20-Aug-84 18':17':07