From owner-freebsd-current@FreeBSD.ORG Wed Jan 29 18:13:35 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 390D05DF for ; Wed, 29 Jan 2014 18:13:35 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB024161A for ; Wed, 29 Jan 2014 18:13:34 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M1nOg-1VGCpi09Aw-00tjgj for ; Wed, 29 Jan 2014 19:13:32 +0100 Message-ID: <52E944CC.5070801@gmx.net> Date: Wed, 29 Jan 2014 19:13:32 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Dmitry Marakasov Subject: Re: [OT] ta-spring References: <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> <20140129144518.GR52820@hades.panopticon> <52E91955.9030406@gmx.net> <20140129163437.GS52820@hades.panopticon> In-Reply-To: <20140129163437.GS52820@hades.panopticon> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:UxGk14sgYIsEjy3VWbDZ1+JjcOFrushTBD5tSKRLzUr1RarsJ/w /vFRYd/EnoNb2RUPLAKKDsXdItRF1KWM4b/NT+HhaC1Su+XDgXMiB+82o4UnLBbpp1l/ouX XsRCFQ+/PfRp//TaUXm3GSSRY2bUg68n8hfXx4Y8FQBocA3q5GV64axkh1CUNi/WSHKyx7j rlGlnhISkDCm1WFMCPaTw== Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 18:13:35 -0000 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