Date: Mon, 23 May 2022 13:17:46 -0400 From: Michael Butler <imb@protected-networks.net> To: Dima Panov <fluffy@FreeBSD.org>, Dimitry Andric <dim@FreeBSD.org>, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: FreeBSD Current <current@freebsd.org>, Brooks Davis <brooks@FreeBSD.org>, FreeBSD Ports Management Team <portmgr@FreeBSD.org> Subject: Re: Bulld failure of editors/libreoffoce only on main (aka -current) Message-ID: <7c977c78-7ad2-8ef8-67b5-41e5271b6e24@protected-networks.net> In-Reply-To: <f2ec74d8-004f-bcbd-f48e-b8b741abd934@FreeBSD.org> References: <20220522082951.f7385d630c23cef986b766e6@dec.sakura.ne.jp> <2ae30822-f07d-53bd-9ed1-09a9a3b4f1f7@FreeBSD.org> <20220524005355.575d32bf574c834cc7305867@dec.sakura.ne.jp> <7B7032E6-5350-4D4C-B542-8F4B5FDB5142@FreeBSD.org> <f2ec74d8-004f-bcbd-f48e-b8b741abd934@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On 5/23/22 12:49, Dima Panov wrote: > My recent -current jail is also have LLVM_DEFAULT=14 and not hit any > serious issue yet:) > > tcberner was initiated exp-run to make llvm13 as default some time ago > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263456 I'd caution against adopting llvm14 for the moment. One apparently architecturally-specific problem with llvm14 on rocketlake (Intel Xeon E-2334 here) is a never-ending compilation in devel/boost-libs if CPUTYPE is set. The file libs/atomic/src/find_address_sse41.cpp causes c++ to run forever :-( It also seems to spin forever with CPUTYPE set to "native". I just found this last night but setting CPUTYPE to "ivybridge" or leaving it unset allows it to run to completion, Michaelhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c977c78-7ad2-8ef8-67b5-41e5271b6e24>