public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/37573] [4.4 Regression] gcc-4.4 regression: incorrect code generation with -O1 -ftree-vectorize
Date: Thu, 18 Sep 2008 19:15:00 -0000	[thread overview]
Message-ID: <20080918191433.2762.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37573-15165@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from pinskia at gcc dot gnu dot org  2008-09-18 19:14 -------
Also fails on powerpc-linux-gnu.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
  GCC build triplet|x86_64-unknown-linux-gnu-   |
                   |gcc-4.4.0                   |
   GCC host triplet|x86_64-unknown-linux-gnu-   |
                   |gcc-4.4.0                   |
 GCC target triplet|x86_64-unknown-linux-gnu-   |
                   |gcc-4.4.0                   |
           Keywords|                            |wrong-code
   Last reconfirmed|0000-00-00 00:00:00         |2008-09-18 19:14:33
               date|                            |
            Summary|gcc-4.4 regression:         |[4.4 Regression] gcc-4.4
                   |incorrect code generation   |regression: incorrect code
                   |with -O1 -ftree-vectorize   |generation with -O1 -ftree-
                   |                            |vectorize
   Target Milestone|---                         |4.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37573


  parent reply	other threads:[~2008-09-18 19:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 17:31 [Bug tree-optimization/37573] New: " edwintorok at gmail dot com
2008-09-18 17:31 ` [Bug tree-optimization/37573] " edwintorok at gmail dot com
2008-09-18 17:33 ` edwintorok at gmail dot com
2008-09-18 19:15 ` pinskia at gcc dot gnu dot org [this message]
2008-09-19 17:03 ` [Bug tree-optimization/37573] [4.4 Regression] " jakub at gcc dot gnu dot org
2008-09-19 17:53 ` jakub at gcc dot gnu dot org
2008-09-21  7:56 ` irar at il dot ibm dot com
2008-10-15 21:30 ` spop at gcc dot gnu dot org
2008-10-15 21:46 ` rguenth at gcc dot gnu dot org
2008-10-15 21:49 ` rguenth at gcc dot gnu dot org
2008-10-16  0:03 ` spop at gcc dot gnu dot org
2008-10-16  8:16 ` rguenther at suse dot de
2008-10-22 16:10   ` Sebastian Pop
2008-10-22  3:29 ` mmitchel at gcc dot gnu dot org
2008-10-22 16:11 ` sebpop at gmail dot com
2008-10-29 18:49 ` edwintorok at gmail dot com
2008-11-03  9:56 ` rguenth at gcc dot gnu dot org
2008-11-03 12:34 ` rguenth at gcc dot gnu dot org
2008-11-03 12:35 ` rguenth at gcc dot gnu dot org
2008-11-03 17:52 ` edwintorok 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=20080918191433.2762.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: link
Be 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).