Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Jan 2014 19:13:32 +0100
From:      Michael Schmiedgen <schmiedgen@gmx.net>
To:        Dmitry Marakasov <amdmi3@amdmi3.ru>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: [OT] ta-spring
Message-ID:  <52E944CC.5070801@gmx.net>
In-Reply-To: <20140129163437.GS52820@hades.panopticon>
References:  <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> <20140129144518.GR52820@hades.panopticon> <52E91955.9030406@gmx.net> <20140129163437.GS52820@hades.panopticon>

next in thread | previous in thread | raw e-mail | index | archive | help
On 29.01.2014 17:34, Dmitry Marakasov wrote:
> * Michael Schmiedgen (schmiedgen@gmx.net) wrote:
>
>> Can we expect a current version of spring in ports soon? That would
>> be nice!
>
> Yes and no. The port is ready, however it's unstable - it crashes on
> start in most cases, however if it doesn't crash on start, it'll work
> without problems. I don't think that's suitable for ports, but since
> 94.1 which is currently in ports has build problems, it may be least
> of two evils.
>
> For now, the port is available for testing here:
>
> https://github.com/AMDmi3/freebsd-ports/tree/master/games/spring
>
>> AFAIK newer versions require OpenMP. Will this compile with
>> our (new 3.4 soon) base clang?
>
> It compiles fine, so either they doesn't use OpenMP or it's
> optional, haven't investigated.
>
> The cause for clang 3.4 experiments is the instability mentioned
> above. Disassembly shows that it crashes on thread-local storage
> access because a null pointer is used as TLS location for some
> reason. I though that it may be a clang 3.3 miscompilation and
> tried 3.4, but there's that libc++ problem.
>
> We can't also build it with GCC, as it depends on boost which is
> built with clang and is thus incompatible with GCC-generated code.
> GCC has another problem, see my following forwarded mail, but that
> can be circumvented in spring code.
>
> My current plans are:
>
> 1) Try to patch system libc++ and try 3.4 again to check if that's
> clang 3.3 specific, however that won't help the port anyway as I
> libc++ can't be patched on all 10.0 systems.
> 2) Try to debug TLS access further. That'd be quite painstaking.
> 3) Write to clang maillist, maybe it's a known problem

Great! Many thanks for your efforts, much appreciated! Let me know if
you need some testing, I run CURRENT on both desktop and laptop,
usually not more than few weeks old. I stay tuned.

Michael




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E944CC.5070801>