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 tree-optimization/42685] New: "-fcompare-debug failure" with "-O1 -funroll-loops" (2) Date: Sun, 10 Jan 2010 23:31:00 -0000 [thread overview] Message-ID: <bug-42685-14164@http.gcc.gnu.org/bugzilla/> (raw) Command line: g++ -O1 -fcompare-debug -funroll-loops -c testcase.cpp -fno-web helps even in the nonreduced testcase Tested revisions: r155777 - crash r155680 - crash r154830 - crash r153685 - crash Output: $ /mnt/svn/gcc-trunk/binary-155777-lto/bin/g++ -O1 -fcompare-debug -funroll-loops -c testcase.cpp g++: testcase.cpp: -fcompare-debug failure Valgrind: no errors reported -- Summary: "-fcompare-debug failure" with "-O1 -funroll-loops" (2) Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zsojka at seznam dot cz GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42685
next reply other threads:[~2010-01-10 23:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-10 23:31 zsojka at seznam dot cz [this message] 2010-01-10 23:33 ` [Bug tree-optimization/42685] " zsojka at seznam dot cz 2010-01-10 23:41 ` zsojka at seznam dot cz 2010-01-12 9:11 ` [Bug tree-optimization/42685] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-12 18:09 ` zsojka at seznam dot cz 2010-01-14 16:39 ` rguenth at gcc dot gnu dot org 2010-01-18 17:00 ` steven at gcc dot gnu dot org 2010-01-18 19:17 ` steven at gcc dot gnu dot org 2010-01-18 19:19 ` steven at gcc dot gnu dot org 2010-01-26 15:15 ` rguenth at gcc dot gnu dot org 2010-01-26 16:28 ` rguenth at gcc dot gnu dot org 2010-01-26 16:28 ` 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=bug-42685-14164@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).