Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eris.berkeley.edu!mwm
From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Same problem after patch
Keywords: My problem or compiler's?
Message-ID: <20427@agate.BERKELEY.EDU>
Date: 15 Feb 89 20:33:37 GMT
References: <9254@bloom-beacon.MIT.EDU> <9256@bloom-beacon.MIT.EDU>
Sender: usenet@agate.BERKELEY.EDU
Organization: Missionaria Phonibalonica
Lines: 31

In article <9256@bloom-beacon.MIT.EDU> tada@athena.mit.edu (Michael Zehr) writes:
<In article <9254@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes:
<>I asked this question about 10 days ago and got a number of
<>answers.  Most blamed the problem on the 5.0 bugs.  I have since
<>installed the 5.02 patch.  I got the patches from the LBBS on 2/8/89.
<> [...]
<>The only way I've been able to get the program to work is to use the CHIP
<>option to BLINK to force everything into chip RAM.  I do not like
<>that solution.  So, what am I doing wrong?
<
<I had similar problems, both with 5.0 and 5.02.  When I called the 
<Lattice technical support people, they offered the following fix:
<
<put all your 'chip' declarations in one module, with no non-chip
<declarations.
<
<from your other modules, declare the references as 'extern chip ...'

I'm not sure the 'chip' is needed. I know it isn't if you use -b0.

As an alternative, you ought to be able to inlclude the 'chip'
structures in with other source, declare them as 'chip' with the
appropriate keyword, and then compile normally. This will _not_ work
with 5.0; you have to have 5.02.

	<mike
--
And then up spoke his own dear wife,			Mike Meyer
Never heard to speak so free.				mwm@berkeley.edu
"I'd rather a kiss from dead Matty's lips,		ucbvax!mwm
Than you or your finery."				mwm@ucbjade.BITNET