From: Jeff Law <law@redhat.com>
To: Richard Biener <rguenther@suse.de>,
Alan Lawrence <alan.lawrence@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR68067
Date: Fri, 06 Nov 2015 16:11:00 -0000 [thread overview]
Message-ID: <563CD115.8010704@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1511061325320.10078@zhemvz.fhfr.qr>
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
next prev parent reply other threads:[~2015-11-06 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 12:50 Richard Biener
2015-10-27 14:31 ` Richard Biener
2015-10-28 13:43 ` Richard Biener
2015-11-06 10:31 ` Alan Lawrence
2015-11-06 10:39 ` Richard Biener
2015-11-06 12:24 ` Alan Lawrence
2015-11-06 12:26 ` Richard Biener
2015-11-06 16:11 ` Jeff Law [this message]
2015-11-20 17:28 ` Alan Lawrence
2015-11-23 9:44 ` Richard Biener
2015-11-27 16:24 ` Alan Lawrence
2015-11-27 18:26 ` Alan Lawrence
2015-11-30 8:52 ` Richard Biener
2015-11-30 17:01 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563CD115.8010704@redhat.com \
--to=law@redhat.com \
--cc=alan.lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).