Re: [Sbcl-devel] SBCL problems on a Mac

[Christophe R. <cs...@ca...>]

Matt Kaufmann <kau...@cs...> writes:

> I think the file was created by someone in Spain, so you're probably right
> about the encoding.
>
>    > ==============================
>    > More serious issue with characters that are a problem for utf-8 encoding:
>    > ==============================
>    >
>    > With
>    >   make regression
>    > while certifying books/defexec/dag-unification/subsumption-subst.lisp:
>    >
>    >   debugger invoked on a SIMPLE-ERROR: segmentation violation at #X1F2EBF0
>
>    I will attempt to reproduce some of this tomorrow, but in the
>    meantime, could you say firstly why you think this is a character
>
> The file in question is one of the few that had characters that created
> problems for the comment reader.
>
>    encoding issue, and secondly whether you have in ACL2 any Lisp code
>    which is compiled under non-safe optimization policies?
>
> Yep, ACL2 is compiled thus:
>
> (proclaim (quote (optimize #+(or cmu sbcl lucid lispworks) (compilation-speed 0)
>                            ;; (debug 0) ; could consider for Lispworks, Allegro
>                            #+cmu (extensions:inhibit-warnings 3)
>                            #+sbcl (sb-ext:inhibit-warnings 3)
>                            (speed 3)
>                            (space #+cmu 1 #-cmu 0) ; no longer necessary?
>                            (safety 0))))

Could you please alter this, for the sake of debugging, to
  (speed 1) (safety 3)
and recompile?  (I understand that this might take a while, but the
extra safety might show up something interesting)

>    A more principled workaround might be to specify 
>      :external-format #+sbcl :iso-8859-1 #-sbcl :default
>    to calls to OPEN / WITH-OPEN-FILE.
>
> Thanks.  That would probably require significantly more ACL2 code changes,
> and/or be harder to maintain; for example, GCL doesn't currently support
> :external-format for with-open-file.  So I'm hoping to get by with the solution
> above.  If that's a grave mistake, I'd be interested in understanding the issue
> better.

Fair enough.  The *default-external-format* solution might well
eventually turn into a supported format, and is unlikely to vanish in
the near future in any case.

>    Your mail is titled "SBCL problems on a Mac".  Do you know whether the
>    problems exist under linux/ppc, or have you only tried Mac OS X?
>
> Sorry about the imprecise Subject.  I have only tried Mac OS X on a Mac.  I've
> used sbcl on linux/x86 without problems.

Right.  Tomorrow I will attempt to reproduce some of these failures on
a ppc with linux; I do have access to a ppc with OS X, but it is
rather slow, so if someone here with access to a faster one has time
to try things that might be good.

Cheers,

Christophe