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 12:08:00 -0000 [thread overview] Message-ID: <20041008120759.15875.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 12:07 ------- Subject: Re: [4.0 Regression] Infinite recursion in tree-scalar-evolution with -Os Here is what the code looks like at the level of my analyzer. loop_0 { bb_0 (preds = {bb_-1}, succs = {bb_0bb_0}) { <bb 0>: if (i_4 != 0) goto <L0>; else goto <L6>; } bb_1 (preds = {bb_0}, succs = {bb_1}) { <L0>:; i_7 = i_4 + 1; } bb_2 (preds = {bb_5bb_1}, succs = {bb_2}) { # i_1 = PHI <i_2(5), i_7(1)>; L:; goto <bb 4> (<L5>); } bb_5 (preds = {bb_0bb_4}, succs = {bb_5bb_5}) { # i_2 = PHI <i_4(0), i_1(4)>; <L6>:; if (i_2 != 1) goto L; else goto <L8>; } bb_6 (preds = {bb_5}, succs = {bb_6}) { <L8>:; return; } loop_1 { bb_3 (preds = {bb_4}, succs = {bb_3}) { <L4>:; j_6 = j_3 + 1; } bb_4 (preds = {bb_3bb_2}, succs = {bb_4bb_4}) { # j_3 = PHI <0(2), j_6(3)>; <L5>:; if (j_3 < i_1) goto <L4>; else goto <L6>; } } } The problem is that we have a cycle "i_1 -> i_2 -> i_1" outside any loop, and I'm not sure about the semantics of this representation. By the way, is this a valid SSA form? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17560
next prev parent reply other threads:[~2004-10-08 12:08 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 [this message] 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 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=20041008120759.15875.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: linkBe 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).