Date: Wed, 19 Nov 2014 00:23:02 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <80988786-733F-4633-ADFB-844FD0DF78EE@FreeBSD.org> In-Reply-To: <20141118200529.GC62527@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <E5857DB5-65CE-4A55-9DF4-B82B86EA7DBB@FreeBSD.org> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> <20140923114447.GB1301@hades.panopticon> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> <20141118200529.GC62527@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Nov 2014, at 21:05, Dmitry Marakasov <amdmi3@amdmi3.ru> wrote: >=20 > * Dimitry Andric (dim@FreeBSD.org) wrote: >=20 >>>>> This seems to be same issue as in >>>>> http://llvm.org/bugs/show_bug.cgi?id=3D20893 for which there is = patch >>>>> review going >>>>> on = http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/23641= 5.html. >>>>>=20 >>>>> Your test case is reproducible with the trunk of llvm/clang and >>>>> the patch in review resolves it. Other workaround is to disable >>>>> generation of debug information by removing -g flag. >>>>=20 >>>> Hm, I had assumed this problem was fixed by importing r203311 from >>>> upstream llvm trunk, in head r263313. But apparently it is not. >>>>=20 >>>> The upstream patch seems to fix your specific test case, but it is = still >>>> in review, so I prefer to wait until it is actually committed, = before I >>>> import it. >>>=20 >>> Which worries me is what we do if it's not reviewd until the = release. We >>> can't just tell users to "remove -g flag", can't we? >>=20 >> I don't expect the review to take very long, but this is how it goes >> with releases. At some point, the release is cut, some bugs don't = get >> fixed, and you will simply have to live with them. >>=20 >> In any case, it entirely depends on how many ports it affects. I = have >> the impression it is just a few particular ports having this issue? >=20 > The bug seem to have been fixed: >=20 > http://llvm.org/bugs/show_bug.cgi?id=3D20893 > http://llvm.org/bugs/show_bug.cgi?id=3D19031 >=20 > This is unfortunately too late for 10.1, but can we possibly have the > fix backported into HEAD and 10-STABLE? Yes, I have already imported the fix in r274442; I will probably get the MFC reminder tomorrow. I'm sorry the fix could not make it into 10.1, but apparently the first version of it was not the proper way of solving the problem. The final version took quite a while, unfortunately. -Dimitry --Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A 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 iEYEARECAAYFAlRr1NoACgkQsF6jCi4glqPg+gCfYfnA2wiRUyiYpXB6R2adQxwR /7AAoMDJVUPsIjtPz9On+Y2RZLXUbYyl =LKwm -----END PGP SIGNATURE----- --Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80988786-733F-4633-ADFB-844FD0DF78EE>