From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6231 invoked by alias); 6 Nov 2015 16:11:04 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 5751 invoked by uid 89); 6 Nov 2015 16:11:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 06 Nov 2015 16:11:03 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 38E1E8F50F; Fri, 6 Nov 2015 16:11:02 +0000 (UTC) Received: from localhost.localdomain (ovpn-113-107.phx2.redhat.com [10.3.113.107]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tA6GB1WP030059; Fri, 6 Nov 2015 11:11:01 -0500 Subject: Re: [PATCH] Fix PR68067 To: Richard Biener , Alan Lawrence References: <563C817D.1060107@arm.com> <563C9BDA.9080002@arm.com> Cc: "gcc-patches@gcc.gnu.org" From: Jeff Law Message-ID: <563CD115.8010704@redhat.com> Date: Fri, 06 Nov 2015 16:11:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00669.txt.bz2 On 11/06/2015 05:26 AM, Richard Biener wrote: > On Fri, 6 Nov 2015, Alan Lawrence wrote: > >> On 06/11/15 10:39, Richard Biener wrote: >>>> ../spec2000/benchspec/CINT2000/254.gap/src/polynom.c:358:11: error: >>>> location >>>> references block not in block tree >>>> l1_279 = PHI <1(28), l1_299(33)> >>> >>> ^^^ >>> >>> this is the error to look at! It means that the GC heap will be corrupted >>> quite easily. >> >> Thanks, I'll have a go at that. >> >> -fdump-tree-alias is also suspicious, hinting that that does more than just >> print. (How many bugs here??) > > Well, it only allocates some more heap memory for extra debug verbosity. > I think this can happen with other dumps as well. Right. Anytime a -fdump-whatever changes behaviour, there's usually some underlying memory issue elsewhere it's tickling. jeff