public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/46799] New: -fcompare-debug failure (length) with -ftree-parallelize-loops=2 -fno-tree-dce Date: Sat, 04 Dec 2010 14:59:00 -0000 [thread overview] Message-ID: <bug-46799-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46799 Summary: -fcompare-debug failure (length) with -ftree-parallelize-loops=2 -fno-tree-dce Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 22630 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22630 reduced testcase Compiler output: $ gcc -O -ftree-parallelize-loops=2 -fno-tree-dce -ftree-pre -fcompare-debug pr46799.c gcc: error: pr46799.c: -fcompare-debug failure (length) $ diff pr46799.*gkd 204c204 < (reg:DI 6 bp))# {*pushdi2_rex64} --- > (reg:DI 6 bp)) pr46799.c:1# {*pushdi2_rex64} 208c208 < (reg:DI 3 bx))# {*pushdi2_rex64} --- > (reg:DI 3 bx)) pr46799.c:1# {*pushdi2_rex64} 217c217 < ])# {pro_epilogue_adjust_stack_di_add} --- > ]) pr46799.c:1# {pro_epilogue_adjust_stack_di_add} 227c227 < (const_int 8 [0x8])) [ .paral_data_load.11_3->D.xxxx+0 S4 A32])) pr46799.c:33554427# {*movsi_internal} --- > (const_int 8 [0x8])) [ .paral_data_load.11_3->D.xxxx+0 S4 A32])) pr46799.c:1# {*movsi_internal} Tested revisions: r167424 - fail r153685 - OK 4.5 r166509 - fail
next reply other threads:[~2010-12-04 14:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-04 14:59 zsojka at seznam dot cz [this message] 2010-12-04 17:09 ` [Bug debug/46799] [4.6 Regression] " hjl.tools at gmail dot com 2010-12-06 10:11 ` jakub at gcc dot gnu.org 2010-12-07 11:28 ` jakub at gcc dot gnu.org 2010-12-07 11:31 ` jakub 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-46799-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).