clang (both 3.3 and 3.4) OOM crashes on HEAD

[Dimitry Andric]

On 23 Sep 2014, at 07:31, Pasi Parviainen <pasi.parviainen at iki.fi> wrote:
> On 23.9.2014 2:10, Dmitry Marakasov wrote:
>> * Dmitry Marakasov (amdmi3 at amdmi3.ru) wrote:
>>>>> I've been getting some failure mails from pkg building cluster related
>>>>> to clang crashes:
>>>>> 
>>>>> http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log
>>>>> http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log
...
>>> http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2
>>> 
>>> The bug is reproducible on my 10.x with both system clang 3.3 (after
>>> removing -vectorize-loops -vectorize-slp options) and with clang 3.4
>>> from ports.
>> 
>> I'll just remind that this is still an issue, and it's getting into
>> 10.1. Could we maybe disable compiler features with lead to these
>> crashes?
>> 
> 
> This seems to be same issue as in http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch review going onhttp://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.

-Dimitry