clang (both 3.3 and 3.4) OOM crashes on HEAD

Dimitry Andric dim at FreeBSD.org
Tue Sep 23 13:05:49 UTC 2014


On 23 Sep 2014, at 13:44, Dmitry Marakasov <amdmi3 at amdmi3.ru> wrote:
> * Dimitry Andric (dim at FreeBSD.org) wrote:
> 
>>> This seems to be same issue as in
>>> http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch
>>> review going
>>> on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html.
>>> 
>>> 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.
>> 
>> Hm, I had assumed this problem was fixed by importing r203311 from
>> upstream llvm trunk, in head r263313.  But apparently it is not.
>> 
>> 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.
> 
> 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?

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.

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?

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-toolchain/attachments/20140923/354b0315/attachment.sig>


More information about the freebsd-toolchain mailing list