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/23115] [4.1 Regression] -ftree-vectorize generates wrong code Date: Fri, 09 Sep 2005 22:19:00 -0000 [thread overview] Message-ID: <20050909221837.32549.qmail@sourceware.org> (raw) In-Reply-To: <20050728183954.23115.p.van-hoof@qub.ac.uk> ------- Additional Comments From janis at gcc dot gnu dot org 2005-09-09 22:18 ------- A regression hunt of mainline on powerpc-linux shows that the test starts failing with a merge from tree-cleanup-branch on 20050409. The test passes, however, with a compiler built after the final patch was added to that branch on 20050401; looks like it could be a merge problem. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |dnovillo at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23115
next prev parent reply other threads:[~2005-09-09 22:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-28 18:40 [Bug tree-optimization/23115] New: " p dot van-hoof at qub dot ac dot uk 2005-07-28 18:43 ` [Bug tree-optimization/23115] " p dot van-hoof at qub dot ac dot uk 2005-07-28 18:54 ` [Bug tree-optimization/23115] [4.1 Regression] " pinskia at gcc dot gnu dot org 2005-09-08 20:03 ` pinskia at gcc dot gnu dot org 2005-09-09 22:19 ` janis at gcc dot gnu dot org [this message] 2005-09-30 23:52 ` dpatel at apple dot com 2005-09-30 23:54 ` pinskia at gcc dot gnu dot org [not found] <bug-23115-1396@http.gcc.gnu.org/bugzilla/> 2005-10-22 21:56 ` pinskia at gcc dot gnu dot org 2005-10-31 4:23 ` mmitchel at gcc dot gnu dot org 2005-11-08 2:23 ` dpatel at apple dot com 2005-11-08 20:21 ` dpatel at gcc dot gnu dot org 2005-11-08 22:13 ` pinskia at gcc dot gnu dot org 2007-07-01 13:40 ` ubizjak at gmail dot com 2007-07-04 5:53 ` ubizjak at gmail dot com
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=20050909221837.32549.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).