Re: state of --with-threads=POSIX_THREADS?

[Vladimir T. <vtz...@gm...>]

I used to test threads builds on 32 bit OSX (even on PowerPC) but haven't
done so in the last year - currently I'm running and testing on 64 bit El
Capitan (10.11.2).
If there is general agreement that it's worthwhile I can spend time on 32
bit OSX support.

Also I'll try to handle timely bug reports for threading issues

--
  Vlad

On Thu, Dec 7, 2017 at 12:20 PM, <Joe...@t-...> wrote:

> Hi,
>
> What's the state of threads in the current clisp? Is it a release target?
> Is it worth opening bug reports about it?
>
> On my 32 bit OSX 10.6.8 machine, and in my environment (no ffcall, no
> sigsegv library!),
> all the regular build-porting-gcc-* expected to build (i.e. not the debug
> one, not the
> gen-gc ones) build fine and pass tests (except the flaky one, bug #720).
>
> However, trying out one of these configurations (the default one) with
> threads
> caused a core dump in threads.tst.
>
> I've not checked out whether one of the many other memory model
> configurations
> would work fine with threads.
>
> [In case you wonder, I'll add libsigsegv to my build environment at a
> later time. After all, I've
> repeated often enough in this list that users should not use clisp without
> it :-)]
>
> Regards,
>         Jörg
>