public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/42640] wrong code for -ftree-loop-distribution in 175.vpr Date: Tue, 23 Feb 2010 19:27:00 -0000 [thread overview] Message-ID: <20100223192731.14681.qmail@sourceware.org> (raw) In-Reply-To: <bug-42640-4503@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from janis at gcc dot gnu dot org 2010-02-23 19:27 ------- The minimized testcase and 175.vpr still fail on powerpc64-linux with "-O2 -ftree-loop-distribution" for both -m32 and -m64. With the confirmation in comment #2 this report ought to be moved from UNCONFIRMED to NEW. This bug is not a regression from 4.4 but it is a wrong-code bug and ought to be considered for fixing in 4.5. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42640
next prev parent reply other threads:[~2010-02-23 19:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-06 23:10 [Bug tree-optimization/42640] New: " janis at gcc dot gnu dot org 2010-01-06 23:12 ` [Bug tree-optimization/42640] " janis at gcc dot gnu dot org 2010-02-08 15:28 ` zsojka at seznam dot cz 2010-02-23 19:27 ` janis at gcc dot gnu dot org [this message] 2010-02-23 20:38 ` bangerth at gmail dot com 2010-02-23 21:07 ` spop at gcc dot gnu dot org 2010-03-02 10:23 ` spop at gcc dot gnu dot org 2010-03-02 10:25 ` spop 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=20100223192731.14681.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).