Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Daniel Barlow <dan@te...> - 2003-01-29 11:57:21
[ Context for SBCL developers:
[ Context for Debian bug reporters: I'm the upstream maintainer for
SBCL alpha, or at least I'm the person who ported it to Alpha, so by
default expected to maintain it... ]
I think there are two bugs represented here:
1) In SBCL versions prior to 0.7.4, we did not flush the icache
properly (at all, actually) between loading code and attempting to
execute it. This often didn't matter on earlier machines, but
ev6 and later will complain bitterly.
This tends to cause random SIGILLS, which is consistent with the
problem reported by Thomas Fischbacher
2) If I'm reading Kalle's message correctly, it suggests that our use
of -mcpu=pca56 is not, strictly speaking, an SBCL bug, but is
probably contraindicated anyway, as unlikely to work on a lot of
stock kernels. For the small amount of C code in SBCL it's
unlikely to make a whole lot of difference, so I'm happy to
take it out.
I'd recommend against using 0.7.2 on Alpha. I can generate a tarchive
of a current (0.7.12 minus pca56, plus one other Alpha patch) SBCL
Alpha binary and make it available for ftp: I'm not however a Debian
developer, and don't have the time or inclination to get involved with
package building, NMUs, or the common-lisp-controller. If anyone else
wants to investigate what's (not) going on with the autobuilders, that
would be cool.
I'll post to this bug again when I have a binary available for ftp.
http://www.cliki.net/ - Link farm for free CL-on-Unix resources