Xref: utzoo comp.sources.d:2122 comp.unix.questions:7053
Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.sources.d,comp.unix.questions
Subject: Re: perl compilation problems
Message-ID: <11532@mimsy.UUCP>
Date: 17 May 88 13:31:53 GMT
References: <240@sdba.UUCP>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 25

In article <240@sdba.UUCP> stan@sdba.UUCP (Stan Brown) writes:
>... the machine that I am working on is a Fortune 32:16
>(a 68000) box.  The error that I am geting occcurs during the compliation
>of perl.c and is something like:
>	... compiler error: no table entry for SASG

Ah yes, everybody's favourite internal PCC error (the fun one is always
`for op REG') :-) .  SASG is almost certainly STASG, STructure ASsiGnment.
It means someone goofed, either leaving an entry out of table.c, or
doing something in the code generator that gets order() stuck with
nowhere to go.

>	    arg[j++] = node[1];
>	    ^^^^^^^^^^^^^^^^^^^

This is somewhat curious, as delay() should have deferred the j++.
But who knows what lurks in the heart of an ancient PCC.

At any rate, there is no way to fix this sort of thing without compiler
sources, and I imagine those are hard to get (did not Fortune quit
making 32:16s?).  About all you can do is experiment with rephrasing
the line of code that triggers the compiler bug.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris