public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/68117] [6 Regression] error: invalid PHI argument <<< Unknown tree: <invalid tree code> >>>
Date: Thu, 29 Oct 2015 13:51:00 -0000 [thread overview]
Message-ID: <bug-68117-4-rY4JtIVPuG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68117-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68117
--- Comment #11 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #10)
> >
> > Valgrind points to r228599:
>
> Nothing obvious but does removing
>
> mark_virtual_operands_for_renaming (cfun);
>
> help? It's the only thing that may end up releasing SSA names
> (if only virtuals).
No, it doesn't help. But reverting r228760 and r228599 fixes the issue.
prev parent reply other threads:[~2015-10-29 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 18:42 [Bug middle-end/68117] New: [6 Regression] ICE: Segmentation fault building Firefox on ppc64le trippels at gcc dot gnu.org
2015-10-28 12:12 ` [Bug middle-end/68117] " rguenth at gcc dot gnu.org
2015-10-28 12:18 ` rguenth at gcc dot gnu.org
2015-10-28 12:27 ` trippels at gcc dot gnu.org
2015-10-28 13:38 ` trippels at gcc dot gnu.org
2015-10-29 8:44 ` [Bug middle-end/68117] [6 Regression] error: invalid PHI argument <<< Unknown tree: <invalid tree code> >>> trippels at gcc dot gnu.org
2015-10-29 10:19 ` rguenth at gcc dot gnu.org
2015-10-29 12:29 ` trippels at gcc dot gnu.org
2015-10-29 13:08 ` rguenther at suse dot de
2015-10-29 13:51 ` trippels at gcc dot gnu.org [this message]
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=bug-68117-4-rY4JtIVPuG@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).