public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian dot pop at cri dot ensmp dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17560] [4.0 Regression] Infinite recursion in tree-scalar-evolution with -Os
Date: Fri, 08 Oct 2004 13:49:00 -0000 [thread overview]
Message-ID: <20041008134913.801.qmail@sourceware.org> (raw)
In-Reply-To: <20040919165202.17560.kherron+gcc@fmailbox.com>
------- Additional Comments From sebastian dot pop at cri dot ensmp dot fr 2004-10-08 13:49 -------
Subject: Re: [4.0 Regression] Infinite recursion in tree-scalar-evolution with -Os
> Could you check whether the edges are marked as irreducible? If not, this would
> be the problem.
>
Indeed, both edges for the phi "i_2 = phi (i_4, i_1)" are not marked
by EDGE_IRREDUCIBLE_LOOP, and consequently backedge_phi_arg_p returns
always false. Same for the first edge i_1 -> i_2 of "i_1 = phi (i_2,
i_7)" that is not marked as EDGE_IRREDUCIBLE_LOOP.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17560
next prev parent reply other threads:[~2004-10-08 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 16:52 [Bug c/17560] New: Segmentation fault compiling prdtoa.c " kherron+gcc at fmailbox dot com
2004-09-19 16:53 ` [Bug c/17560] " kherron+gcc at fmailbox dot com
2004-09-19 16:55 ` kherron+gcc at fmailbox dot com
2004-09-19 19:19 ` [Bug tree-optimization/17560] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-09-20 2:00 ` reichelt at gcc dot gnu dot org
2004-09-20 2:02 ` reichelt at gcc dot gnu dot org
2004-09-20 2:08 ` pinskia at gcc dot gnu dot org
2004-09-27 21:29 ` pinskia at gcc dot gnu dot org
2004-10-07 18:55 ` reichelt at gcc dot gnu dot org
2004-10-07 21:31 ` pinskia at gcc dot gnu dot org
2004-10-07 22:54 ` pinskia at gcc dot gnu dot org
2004-10-08 1:16 ` [Bug tree-optimization/17560] [4.0 Regression] Infinite recursion in tree-scalar-evolution " reichelt at gcc dot gnu dot org
2004-10-08 3:27 ` pinskia at gcc dot gnu dot org
2004-10-08 12:08 ` sebastian dot pop at cri dot ensmp dot fr
2004-10-08 12:39 ` Diego Novillo
2004-10-08 12:16 ` hubicka at ucw dot cz
2004-10-08 12:39 ` dnovillo at redhat dot com
2004-10-08 13:03 ` sebastian dot pop at cri dot ensmp dot fr
2004-10-08 13:09 ` Diego Novillo
2004-10-08 13:10 ` dnovillo at redhat dot com
2004-10-08 13:22 ` rakdver at gcc dot gnu dot org
2004-10-08 13:49 ` sebastian dot pop at cri dot ensmp dot fr [this message]
2004-10-08 20:17 ` rakdver at gcc dot gnu dot org
2004-10-09 8:00 ` rakdver at gcc dot gnu dot org
2004-10-11 10:28 ` reichelt at gcc dot gnu dot org
2004-10-16 16:45 ` cvs-commit at gcc dot gnu dot org
2004-10-16 16:46 ` rakdver at gcc dot gnu dot org
2004-10-17 19:16 ` reichelt at gcc dot gnu dot org
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=20041008134913.801.qmail@sourceware.org \
--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).