Date: Mon, 1 Dec 2014 19:20:17 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: FreeBSD ARM <freebsd-arm@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org>, FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: RFT: Please help testing the llvm/clang 3.5.0 import Message-ID: <B595A254-D318-48DB-8002-30A4085D9726@FreeBSD.org> In-Reply-To: <20141201175407.GA14863@hades.panopticon> References: <8598B1D4-5485-426F-B6D6-22BF26AC5FE1@FreeBSD.org> <20141130185730.GA73028@hades.panopticon> <4E415461-2B00-4F02-B7F6-B3A595B4FB20@FreeBSD.org> <20141201175407.GA14863@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_FA78DF12-9A94-4E40-AFD8-1191C024EF34 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 01 Dec 2014, at 18:54, Dmitry Marakasov <amdmi3@amdmi3.ru> wrote: > > * Dimitry Andric (dim@FreeBSD.org) wrote: > >>>> We're working on updating llvm, clang and lldb to 3.5.0 in head. >>>> This is quite a big update again, and any help with testing is >>>> appreciated. >>> >>> Well, of 4 error logs from exp-run I've checked (one my port and 3 >>> unmaintained ports) two had basically the same problem and it seems >>> to be libc++ related, so I ask: was new version of libc++ imported >>> along with clang/llvm? >> >> No, I really prefer to do this after the 3.5.0 import. This is already >> a very big import job, and I'd rather like to avoid importing too many >> different components at once. >> >> >>> Past experience show that libc++ should be >>> updated along with clang, as it may have bugs new clang versions >>> are not tolerable to. >> >> In this case, there is a fairly simple fix: >> http://llvm.org/viewvc/llvm-project?view=revision&revision=209785 >> >> I have pulled this into head in r275366, and also merged it to the >> clang350-import project branch in r275367. Please try again after that >> revision. It should be enough to just rebuild lib/libc++ and install >> it. > > Sorry, I haven't tested the branch myself, only seen exp-run results. > Would be nice to have another exp-run. Yes, but we first need to fix another issue, which is more important: several of the lang/gcc ports don't work properly, e.g. bootstrap stage comparison fails. There is also something fishy going on with gcc in base, which may or may not be related: building the devel/binutils ports with it causes cc1plus to segfault while compiling gold's archive.cc. I am still searching for the root cause; any help in this area would be greatly appreciated, as the maintainer has not responded yet. > Btw, is it possible to merge the patch into stable/10 as well? > It will make it possible to use clang35 there. Yes, this is also why I prefer to cherry-pick; I have set an MFC timeout of 3 days. -Dimitry --Apple-Mail=_FA78DF12-9A94-4E40-AFD8-1191C024EF34 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlR8sXUACgkQsF6jCi4glqOs/QCeKELV2EMIrKFpDTdqsJGlqXsI RXIAn3llBJqihAkHStk2+Cz9mwYYlJAd =2yTy -----END PGP SIGNATURE----- --Apple-Mail=_FA78DF12-9A94-4E40-AFD8-1191C024EF34--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B595A254-D318-48DB-8002-30A4085D9726>