public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61757] [4.10 Regression] genmodes failure with enable-checking
Date: Mon, 14 Jul 2014 19:15:00 -0000	[thread overview]
Message-ID: <bug-61757-4-HJ0sLjA1g0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61757-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61757

--- Comment #32 from Jeffrey A. Law <law at redhat dot com> ---
No, we don't have that information available in any reasonable form.  That's
one of the things I need to investigate.

One of the possibilities is to flip things on their side a bit.  The old code
started recording equivalences it might need to invalidate when it traversed
the backedge.  Part of the problem with that scheme is some of the equivalences
were already recorded by tree-ssa-dom.c, independent of the threading bits.  We
didn't have a way to find or invalidate those equivalences.

One of the things I want to look at is whether or not we can start recording
when we process a PHI with arguments that are the targets of backedges.  I
haven't prototyped any code around that and I'm not sure if we'll have a
reasonable separation between DOM and the threading code, but that's the first
thing I want to look at once I deal with Teresa's changes.


  parent reply	other threads:[~2014-07-14 19:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  7:51 [Bug bootstrap/61757] New: " dcb314 at hotmail dot com
2014-07-09  8:56 ` [Bug bootstrap/61757] " dominiq at lps dot ens.fr
2014-07-09 10:14 ` ktkachov at gcc dot gnu.org
2014-07-09 11:56 ` [Bug bootstrap/61757] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-07-09 12:45 ` [Bug tree-optimization/61757] " schwab@linux-m68k.org
2014-07-09 13:09 ` schwab@linux-m68k.org
2014-07-09 20:47 ` dominiq at lps dot ens.fr
2014-07-10  9:36 ` rguenth at gcc dot gnu.org
2014-07-10  9:39 ` ktkachov at gcc dot gnu.org
2014-07-10 10:29 ` schwab@linux-m68k.org
2014-07-10 14:43 ` rguenth at gcc dot gnu.org
2014-07-10 14:49 ` rguenth at gcc dot gnu.org
2014-07-11 13:29 ` rguenth at gcc dot gnu.org
2014-07-11 13:45 ` dominiq at lps dot ens.fr
2014-07-11 14:07 ` ro at gcc dot gnu.org
2014-07-11 14:26 ` schwab@linux-m68k.org
2014-07-11 16:16 ` pthaugen at gcc dot gnu.org
2014-07-11 17:24 ` matz at gcc dot gnu.org
2014-07-11 17:47 ` matz at gcc dot gnu.org
2014-07-11 18:32 ` schwab@linux-m68k.org
2014-07-11 23:03 ` pthaugen at gcc dot gnu.org
2014-07-13 13:39 ` dominiq at lps dot ens.fr
2014-07-13 17:32 ` segher at gcc dot gnu.org
2014-07-14  1:23 ` danglin at gcc dot gnu.org
2014-07-14  8:56 ` rguenth at gcc dot gnu.org
2014-07-14  9:04 ` rguenth at gcc dot gnu.org
2014-07-14  9:17 ` rguenth at gcc dot gnu.org
2014-07-14  9:48 ` rguenth at gcc dot gnu.org
2014-07-14 10:51 ` rguenth at gcc dot gnu.org
2014-07-14 10:51 ` rguenth at gcc dot gnu.org
2014-07-14 17:57 ` pthaugen at gcc dot gnu.org
2014-07-14 19:15 ` law at redhat dot com [this message]
2014-07-15  7:45 ` rguenther at suse dot de
2015-01-16  5:37 ` law at redhat dot com

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-61757-4-HJ0sLjA1g0@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).