Hello Paul,

We've historically had different test results on FreeBSD/x86-64 between threaded and non-threaded builds, with the threaded builds coming out the poorer.  A couple of my commits in this release are supposed to address the worst of this difference, so I'm curious, are these threaded or non-threaded builds?  Or do both versions have the same results on both platforms?

Thanks,

-- Alastair Bridgewater

On May 25, 2013 8:05 PM, "Paul Khuong" <pvk@pvk.ca> wrote:
>
> x86-64:
>   Expected failure:   compiler.pure.lisp /
> FOLD-INDEX-ADDRESSING-POSITIVE-OFFSET
>   Expected failure:   interface.pure.lisp / (SLEEP NON-CONSING)
>   Expected failure:   dynamic-extent.impure.lisp / (NO-CONSING
> SPECIALIZED-DX-VECTORS)
>   Expected failure:   packages.impure.lisp / USE-PACKAGE-CONFLICT-SET
>   Expected failure:   packages.impure.lisp / IMPORT-SINGLE-CONFLICT
>   Expected failure:   walk.impure.lisp / (WALK-LET* HAIRY-SPECIALS)
>   Expected failure:   walk.impure.lisp / (WALK-LET* HAIRY-SPECIALS)
>
> x86:
>   Expected failure:   compiler.pure.lisp /
> FOLD-INDEX-ADDRESSING-POSITIVE-OFFSET
>   Unexpected success: debug.impure.lisp / (UNDEFINED-FUNCTION BUG-346)
>   Failure:            debug.impure.lisp /
> BACKTRACE-INTERRUPTED-CONDITION-WAIT
>   Expected failure:   packages.impure.lisp / USE-PACKAGE-CONFLICT-SET
>   Expected failure:   packages.impure.lisp / IMPORT-SINGLE-CONFLICT
>   Expected failure:   walk.impure.lisp / (WALK-LET* HAIRY-SPECIALS)
>   Expected failure:   walk.impure.lisp / (WALK-LET* HAIRY-SPECIALS)
>
> Paul Khuong
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Sbcl-devel mailing list
> Sbcl-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel