public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/56605] Redundant branch introduced during loop2 phases Date: Tue, 12 Mar 2013 19:54:00 -0000 [thread overview] Message-ID: <bug-56605-4-Inuo5TF3ie@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56605-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56605 --- Comment #1 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-12 19:54:05 UTC --- Confirmed, compiling with -mcpu=power7 -msvx -O3 -fno-unroll-loops Comes from here: Breakpoint 8, doloop_modify (loop=0x3fffb5dc0ee0, desc=0x111d6d00, doloop_seq=0x3fffb5f35780, condition=0x3fffb5fd1680, count=0x3fffb5fd16e0) at ../../trunk/gcc/loop-doloop.c:505 505 for (; ass; ass = XEXP (ass, 1)) (gdb) p debug_rtx(ass) (expr_list:REG_DEP_TRUE (eq:SI (subreg:SI (reg:DI 153) 4) (const_int 0 [0])) (expr_list:REG_DEP_TRUE (eq:SI (subreg:SI (reg:DI 153) 4) (const_int 0 [0])) (nil))) $51 = void (gdb) These are the noloop_assumptions, and the same assertion appears twice.
next prev parent reply other threads:[~2013-03-12 19:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-12 18:57 [Bug rtl-optimization/56605] New: " wschmidt at gcc dot gnu.org 2013-03-12 19:20 ` [Bug rtl-optimization/56605] " steven at gcc dot gnu.org 2013-03-12 19:54 ` steven at gcc dot gnu.org [this message] 2013-03-12 23:00 ` steven at gcc dot gnu.org 2013-03-12 23:15 ` steven at gcc dot gnu.org 2013-04-15 18:32 ` wschmidt at gcc dot gnu.org 2013-04-23 19:49 ` wschmidt 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-56605-4-Inuo5TF3ie@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).