Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Nov 2014 23:05:29 +0300
From:      Dmitry Marakasov <amdmi3@amdmi3.ru>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org
Subject:   Re: clang (both 3.3 and 3.4) OOM crashes on HEAD
Message-ID:  <20141118200529.GC62527@hades.panopticon>
In-Reply-To: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
* Dimitry Andric (dim@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?

The bug seem to have been fixed:

http://llvm.org/bugs/show_bug.cgi?id=20893
http://llvm.org/bugs/show_bug.cgi?id=19031

This is unfortunately too late for 10.1, but can we possibly have the
fix backported into HEAD and 10-STABLE?

-- 
Dmitry Marakasov   .   55B5 0596 FF1E 8D84 5F56  9510 D35A 80DD F9D2 F77D
amdmi3@amdmi3.ru  ..:  jabber: amdmi3@jabber.ru    http://www.amdmi3.ru



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141118200529.GC62527>