Xref: utzoo comp.sources.bugs:776 comp.unix.questions:5693
Path: utzoo!mnetor!uunet!husc6!psuvax1!vu-vlsi!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.sources.bugs,comp.unix.questions
Subject: Re: System V yacc / perl problem
Message-ID: <3328@cbmvax.UUCP>
Date: 16 Feb 88 21:21:31 GMT
References: <1675@van-bc.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 26
Keywords: yacc perl sysv

In article <1675@van-bc.UUCP> sl@van-bc.UUCP (Stuart Lynne) writes:
> Weirdness abounds once again! 
> 
> I can successfully generate perl on my ancient Callan (a Unisoft 5.0 system, 
> basically System V release level 0 with some BSD ism's), but not on my modern,
> uptodate, state of the art System V release 3 for the 386 at work!!!
> 
> The problem is yacc. I get the following results when make try's to generate
> perl.c from perl.y:
...
> 	 fatal error: out of state space, line 595

Well, I have the same problem on my creaky old Zilog system.  I don't know
if yacc is actually runninng out of memory, or if it's just that in a binary
release, you get a version of yacc compiled with the parameters set to fit
the "worst case" i.e. PDP-11 / Zilog non-segmented / 8088 small-model
memory constraints...

I would be helpful if Larry could include the yacc output, with the 
makefile set up to only redo the yacc run in the critical input files
changed, but of course this would make the release bigger...

-- 
George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)