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/42642] "-fcompare-debug failure" with "-O1 -fpeel-loops" Date: Thu, 07 Jan 2010 00:39:00 -0000 [thread overview] Message-ID: <20100107003904.21868.qmail@sourceware.org> (raw) In-Reply-To: <bug-42642-14164@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from zsojka at seznam dot cz 2010-01-07 00:39 ------- Created an attachment (id=19494) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19494&action=view) reduced testcase Command line: g++ -O1 -fpeel-loops -fcompare-debug pr42642.cpp -c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42642
next prev parent reply other threads:[~2010-01-07 0:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-07 0:38 [Bug tree-optimization/42642] New: " zsojka at seznam dot cz 2010-01-07 0:39 ` zsojka at seznam dot cz [this message] 2010-01-07 7:17 ` [Bug tree-optimization/42642] " steven at gcc dot gnu dot org 2010-01-07 12:50 ` zsojka at seznam dot cz 2010-01-18 16:58 ` steven at gcc dot gnu dot org 2010-01-18 17:45 ` zsojka at seznam dot cz 2010-01-18 18:31 ` steven at gcc dot gnu dot org 2010-01-18 19:19 ` steven 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=20100107003904.21868.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).