From: Paul Snively
Subject: Re: Apple CL incompatible with Radius accelorater
Date:
Message-ID: <4819@internal.Apple.COM>
In article <··················@brazil.cambridge.apple.com>
····@cambridge.apple.com (Andrew L. M. Shalit) writes:
> In article <····@internal.Apple.COM> ·····@apple.com (Paul Snively)
writes:
>
> In article <········@yvax.byu.edu> ·····@yvax.byu.edu writes:
> > I just installed a Radius 16 mhz accelorater board in my SE and
> > find that
> > Apple Allegro CL will not boot. I get the bomb!, error=11. So
far,
> > Radius blames Apple, and I haven't received a reply back from my
> > AppleLink query to Apple. I don't suppose anyone out there has had
any
> > experience? Any ideas would be appreciated.
>
> Yup, it's our problem. Put this patch in your INIT.LISP file:
>
> [spurious patch deleted]
>
> Whoops. The patch which Paul posted will not fix the Radius bug.
>
> Radius boards sans FPU do not generate FTRAPs correctly. MACL depends
> on correct FTRAP behavior (this lets us generate object code which
> runs on a variety of Macs). We're in the process of trying to get in
> touch with someone at Radius so we can fix this problem.
>
> In the meantime, getting an FPU may help.
Whoops, indeed. While the patch I posted doesn't solve the problem in
question, it DOES solve other floating-point errors in the versions of
Macintosh Allegro Common Lisp that I mentioned.
As for the Radius problem, getting an FPU not only MAY help, it DOES help.
__________________________________________________________________________
Just because I work for Apple Computer, Inc. doesn't mean that they
believe what I believe or vice-versa.
__________________________________________________________________________
C++ -- The language in which only friends can access your private members.
__________________________________________________________________________