public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61068] [4.8 Regression] -O3 generates bad code (when tree-vectorize or inline-functions is on)
Date: Tue, 06 May 2014 08:53:00 -0000	[thread overview]
Message-ID: <bug-61068-4-F8IGghbdhT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61068-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-*
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |4.7.3, 4.9.0
   Last reconfirmed|                            |2014-05-06
          Component|target                      |tree-optimization
                 CC|                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1
            Summary|-O3 generates bad code      |[4.8 Regression] -O3
                   |(when tree-vectorize or     |generates bad code (when
                   |inline-functions is on)     |tree-vectorize or
                   |                            |inline-functions is on)
   Target Milestone|---                         |4.8.3
      Known to fail|                            |4.8.2

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed on x86_64-linux with -O3 -fPIC (default on darwin) and with
-O2 -ftree-vectorize -funroll-loops -fPIC.

There are a few vectorizer wrong-code bugs on the 4.8 branch that I haven't
managed to backport yet from 4.9.  4.7 seems to work.


  parent reply	other threads:[~2014-05-06  8:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 16:07 [Bug c/61068] New: " wence at gmx dot li
2014-05-05 16:40 ` [Bug c/61068] " wence at gmx dot li
2014-05-05 16:46 ` [Bug target/61068] " mpolacek at gcc dot gnu.org
2014-05-05 20:28 ` zsojka at seznam dot cz
2014-05-06  6:13 ` wence at gmx dot li
2014-05-06  8:53 ` [Bug tree-optimization/61068] [4.8 Regression] " rguenth at gcc dot gnu.org
2014-05-06  8:53 ` rguenth at gcc dot gnu.org [this message]
2014-05-06  9:22 ` jakub at gcc dot gnu.org
2014-05-06  9:25 ` rguenth at gcc dot gnu.org
2014-05-06 10:13 ` rguenth at gcc dot gnu.org
2014-05-22  9:03 ` rguenth at gcc dot gnu.org
2014-12-10 12:59 ` rguenth at gcc dot gnu.org
2014-12-19 13:31 ` jakub at gcc dot gnu.org
2015-06-23  8:52 ` rguenth at gcc dot gnu.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-61068-4-F8IGghbdhT@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: 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).