public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/45792] New: [4.6 Regression]: cris-elf build failure (hangs) due to fix for PR44374 Date: Sat, 25 Sep 2010 19:06:00 -0000 [thread overview] Message-ID: <bug-45792-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45792 Summary: [4.6 Regression]: cris-elf build failure (hangs) due to fix for PR44374 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: hp@gcc.gnu.org CC: bernds@gcc.gnu.org Host: x86_64-unknown-linux-gnu Target: cris-*-* Created attachment 21882 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=21882 Preprocessed dtoa.c At r164551 the tree built with few regressions. At r164560 building newlib/libc/stdlib/dtoa.c hangs (cpu-time > 38 hours) and at r164619 the build is at a similar state (didn't wait 38 hours, but see below). Attaching a gdb-session to the running cc1 at r164619 shows an infinite loop in gcc/emit-rtl.c:reorder_insns: 4027 for (x = from; x != NEXT_INSN (to); x = NEXT_INSN (x)) 4028 if (!BARRIER_P (x)) 4029 df_insn_change_bb (x, bb); But "x" is bogus; it seems to have been deleted or at least removed from the insn stream: (insn 2210 2210 2210 239 (set (cc0) (compare (reg/v/f:SI 3 r3 [orig:95 mlo ] [95]) (reg/v/f:SI 4 r4 [orig:97 mhi ] [97]))) /tmp/hpautotest-gcc1/gcc/newlib/libc/stdlib/dtoa.c:808 11 {*cmpsi} (nil)) The call to df_insn_change_bb takes the (old_bb == new_bb) early return. Author of suspect patch in revision range CC:ed. Preprocessed dtoa.c attached. Compile with -O2.
next reply other threads:[~2010-09-25 16:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-25 19:06 hp at gcc dot gnu.org [this message] 2010-09-25 19:08 ` [Bug rtl-optimization/45792] " hp at gcc dot gnu.org 2010-09-26 4:17 ` hp at gcc dot gnu.org 2010-09-27 11:52 ` hp at gcc dot gnu.org 2010-09-27 12:11 ` bernds at gcc dot gnu.org 2010-09-27 19:35 ` hp at gcc dot gnu.org 2010-09-28 10:58 ` hp at gcc dot gnu.org 2010-09-28 11:01 ` hp 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-45792-4@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).