public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55011] [4.8 Regression] GCC in an infinite loop at -O2 in VRP Date: Mon, 22 Oct 2012 10:04:00 -0000 [thread overview] Message-ID: <bug-55011-4-p57XMKhnLn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55011-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55011 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2012-10-22 10:03:56 UTC --- We are iterating between Visiting PHI node: s_56 = PHI <_53(3), _12(12)> Argument #0 (3 -> 4 executable) _53 Value: [63740, +INF] EQUIVALENCES: { _19 } (1 elements) Argument #1 (12 -> 4 executable) _12 Value: UNDEFINED Meeting [63740, +INF] EQUIVALENCES: { _19 } (1 elements) and UNDEFINED to [63740, +INF] EQUIVALENCES: { } (0 elements) Found new range for s_56: [63740, +INF] Simulating statement (from ssa_edges): s_56 = PHI <_53(3), _12(12)> Visiting PHI node: s_56 = PHI <_53(3), _12(12)> Argument #0 (3 -> 4 executable) _53 Value: UNDEFINED Argument #1 (12 -> 4 executable) _12 Value: UNDEFINED Meeting UNDEFINED and UNDEFINED to UNDEFINED Found new range for s_56: UNDEFINED Simulating statement (from ssa_edges): s_56 = PHI <_53(3), _12(12)> Visiting PHI node: s_56 = PHI <_53(3), _12(12)> Argument #0 (3 -> 4 executable) _53 Value: [63740, +INF] EQUIVALENCES: { _19 } (1 elements) Argument #1 (12 -> 4 executable) _12 Value: UNDEFINED Meeting [63740, +INF] EQUIVALENCES: { _19 } (1 elements) and UNDEFINED to [63740, +INF] EQUIVALENCES: { } (0 elements) Found new range for s_56: [63740, +INF] which means _53 has bogus transitions: Visiting statement: _53 = ASSERT_EXPR <_19, _19 > 63739>; Intersecting [63740, +INF] EQUIVALENCES: { _19 } (1 elements) and [0, +INF] to [63740, +INF] EQUIVALENCES: { _19 } (1 elements) Found new range for _53: [63740, +INF] Visiting statement: _53 = ASSERT_EXPR <_19, _19 > 63739>; Intersecting [63740, +INF] EQUIVALENCES: { _19 } (1 elements) and [15935, 32767] to UNDEFINED Found new range for _53: UNDEFINED I have a patch.
next prev parent reply other threads:[~2012-10-22 10:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-21 18:31 [Bug middle-end/55011] New: GCC in an infinite loop at -O2 antoine.balestrat at gmail dot com 2012-10-22 9:04 ` [Bug tree-optimization/55011] [4.8 Regression] GCC in an infinite loop at -O2 in VRP rguenth at gcc dot gnu.org 2012-10-22 9:26 ` jakub at gcc dot gnu.org 2012-10-22 9:44 ` rguenth at gcc dot gnu.org 2012-10-22 10:04 ` rguenth at gcc dot gnu.org [this message] 2012-10-22 13:27 ` rguenth at gcc dot gnu.org 2012-10-22 13:27 ` rguenth at gcc dot gnu.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=bug-55011-4-p57XMKhnLn@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: 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).