patch (was [Sbcl-devel] two bugs?)

[Martin A. <ma...@at...>]

Martin Atzmueller wrote:

> "Brown, Robert E (FICC)" wrote:
> 
> > I tried building the HEAD revision of sbcl using both sbcl and cmucl.  I got
> > the same error each time.  I'll try again.  Maybe I need a newer sbcl to
> > build the latest sbcl?
[...]
> As I wrote before, using cmucl-18c won't probably work.
> One problem again - in using cmucl, as I see it just now, is that it
> causes "warnings" about some "undefined" functions, when building
> the cross-compiler.
> These functions are compiled later, but are being referenced in code
> to be compiled previously.
> And since sbcl takes these warnings seriously, it won't proceed in
> the compilation process.
Well, I think I have to rectify this remark: the "warnings about
undefined functions" are not the reason, why CMUCL won't compile
current CVS-sbcl (0.6.12.48).
[At least, if the functions are defined later ;),
and this seems to work!]
The reason is another warning:

Actually, a bug has crept into SBCL (I think it was introduced in
0.6.12.45):
FIX-CORE-SOURCE-INFO (in src/compiler/generic/core.lisp)
should take three arguments, but is defined to take two,
and it's called both with two and three arguments.
So, CMUCL issues a WARNING, and that blows up compilation, at least
that's what happens in cmucl-18c.

The attached patch corrects for this, and now cmucl-18c happily builds
SBCL again.

-- 
Martin Atzmueller <ma...@at...>