Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!bellcore!faline!thumper!ulysses!andante!alice!debra
From: debra@alice.UUCP (Paul De Bra)
Newsgroups: comp.unix.xenix
Subject: Re: SCO Xenix 386 infinite spill
Message-ID: <8362@alice.UUCP>
Date: 27 Oct 88 21:08:35 GMT
References: <225@milhow1.UUCP>
Reply-To: debra@alice.UUCP ()
Organization: AT&T, Bell Labs
Lines: 26

In article <225@milhow1.UUCP> how@milhow1.UUCP (Mike Howard) writes:
>Background: I am putting up TeX on an SCO Xenix 386 system using the
> web2c distribution.  The vanilla SYSV distribution is translating
> and compiling without errors except that the compiler dies on an
> `infinite spill' error.
>
Most infinite spill-problems I have seen all are of the form
array1[array2[some index expression]+some expression]=
array1[array2[array3[expression]+expression]+expression];
or something like that. A combination of array-indexes cause the compiler
to choke.
But I believe the problem is even more subtile: taking the one expression
out of its context makes the problem go away. Obviously the compiler is
incrementing a counter somewhere and when it doesn't advance far enough in
the source-code for a number of counter-increments it decides that it is
in an infinite spill.

A sufficient way to get rid of the infinite spill messages is to never
index an array with another array-reference. But doing this automatically
generates a large number of temporary variables.

Paul.
-- 
-------------------------------------------------------------------------
|debra@research.att.com   | uunet!research!debra     | att!grumpy!debra |
-------------------------------------------------------------------------