From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 17:59:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62026F90; Tue, 23 Sep 2014 17:59:31 +0000 (UTC) Received: from smtpout1.timeweb.ru (smtpout1.timeweb.ru [92.53.117.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F315A7; Tue, 23 Sep 2014 17:59:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=PFr/udPhUhdHcqCxWxva2GKdwN7gKpXdEG7L3eIAd24=; b=OjlLP5PluI9U6UE7lP7I9qfB/ZcR6utZnTyopr0TO/7HDfMAXz4q5shoAR270zRACt0pC01tWMHuYqyAzOAlViatr9A/jskskzOpU84cRe73jisaqiHGPcQX5ouLyUQBSxVek7uGJySgbZJMzTgg79qPuc4QpAm4NhEC3c3LZJI=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWUN1-0006qx-8D; Tue, 23 Sep 2014 21:59:23 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 93557549; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 6DFF619213; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Date: Tue, 23 Sep 2014 21:59:22 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140923175922.GA98560@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org, Pasi Parviainen X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 17:59:31 -0000 * 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. That seems too critical for me to live with it. > 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? Probably yes, but more important is user's private code which may be also affected. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru