public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/39999] gcc 4.4.0 compiles in infinite loop Date: Sat, 02 May 2009 10:20:00 -0000 [thread overview] Message-ID: <20090502101957.23954.qmail@sourceware.org> (raw) In-Reply-To: <bug-39999-11113@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2009-05-02 10:19 ------- Confirmed. I hit #ifdef ENABLE_CHECKING /* Theoretically possible, but *highly* unlikely. */ gcc_assert (num_iterations < 500); #endif on trunk. We seem to oscillate .... ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A1_1,-4} (0026), {pointer_plus_expr,A2_2,-4} (0046) } ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A2_2,-4} (0025), {pointer_plus_expr,A2_2,-4} (0046) } ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A1_1,-4} (0026), {pointer_plus_expr,A2_2,-4} (0046) } ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A2_2,-4} (0025), {pointer_plus_expr,A2_2,-4} (0046) } ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A1_1,-4} (0026), {pointer_plus_expr,A2_2,-4} (0046) } ANTIC_IN[12] := { A1_1 (0001), A2_2 (0002), {pointer_plus_expr,A2_2,-4} (0025), {pointer_plus_expr,A2_2,-4} (0046) } Maybe we get confused by the degenerate PHIs <bb 22>: <bb 14>: # A1_17 = PHI <A1_1(22)> # A2_18 = PHI <A2_2(22)> C_29 = MMAPMON (p_8(D), A2_18); D.1783_30 = A2_18 + -4; free (D.1783_30); D.1784_31 = A1_17 + -4; -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org, rguenth at gcc dot gnu | |dot org Status|UNCONFIRMED |NEW Component|middle-end |tree-optimization Ever Confirmed|0 |1 Keywords| |ice-on-valid-code Last reconfirmed|0000-00-00 00:00:00 |2009-05-02 10:19:57 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39999
next prev parent reply other threads:[~2009-05-02 10:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-01 22:43 [Bug c/39999] New: " howarth at nitro dot med dot uc dot edu 2009-05-01 22:49 ` [Bug middle-end/39999] " pinskia at gcc dot gnu dot org 2009-05-01 23:00 ` howarth at nitro dot med dot uc dot edu 2009-05-02 10:20 ` rguenth at gcc dot gnu dot org [this message] 2009-05-06 13:25 ` [Bug tree-optimization/39999] [4.4/4.5 Regression] " rguenth at gcc dot gnu dot org 2009-05-06 13:53 ` rguenth at gcc dot gnu dot org 2009-05-06 15:30 ` mmitchel at gcc dot gnu dot org 2009-05-15 13:10 ` rguenth at gcc dot gnu dot org 2009-05-15 13:10 ` [Bug tree-optimization/39999] [4.4 " rguenth at gcc dot gnu dot org 2009-05-15 13:38 ` howarth at nitro dot med dot uc dot edu 2009-05-15 13:47 ` rguenther at suse dot de 2009-05-18 10:14 ` rguenth at gcc dot gnu dot org 2009-05-18 10:14 ` rguenth 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=20090502101957.23954.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).