From owner-freebsd-current@FreeBSD.ORG Wed Jan 29 16:34:46 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 955BC606 for ; Wed, 29 Jan 2014 16:34:46 +0000 (UTC) Received: from smtpout3.timeweb.ru (smtpout3.timeweb.ru [92.53.117.25]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4AA041D65 for ; Wed, 29 Jan 2014 16:34:46 +0000 (UTC) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1W8Y61-000300-P8; Wed, 29 Jan 2014 20:34:37 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 50CB7802; Wed, 29 Jan 2014 20:34:37 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 3587B1CED3; Wed, 29 Jan 2014 20:34:37 +0400 (MSK) Date: Wed, 29 Jan 2014 20:34:37 +0400 From: Dmitry Marakasov To: Michael Schmiedgen Subject: Re: [OT] ta-spring Message-ID: <20140129163437.GS52820@hades.panopticon> References: <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> <20140129144518.GR52820@hades.panopticon> <52E91955.9030406@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <52E91955.9030406@gmx.net> User-Agent: Mutt/1.5.22 (2013-10-16) 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 16:34:46 -0000 * Michael Schmiedgen (schmiedgen@gmx.net) wrote: > >> Hm, which port is having problems with this? I have built quite a large > >> set, and never encountered this issue. > >> > >> In any case: yes, it is quite long overdue for a libc++ update. :-) I > >> will have a look tonight. > > > > New version of games/spring (not in ports yet). > > 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 -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru