public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56864] [4.9 regression] FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c scan-tree-dump-times vect "vectorized 1 loops" 0
Date: Thu, 02 May 2013 15:55:00 -0000	[thread overview]
Message-ID: <bug-56864-4-N2PRbFMeTh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56864-4@http.gcc.gnu.org/bugzilla/>


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

Bill Schmidt <wschmidt at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #10 from Bill Schmidt <wschmidt at gcc dot gnu.org> 2013-05-02 15:55:07 UTC ---
Well, I still can't find the magic to reproduce this myself, but our overnight
tester shows the failure
(http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg00094.html).

Richi, this is another test that started failing with the same commit as
PR56865.  In this case, it appears we are now vectorizing a loop that we
formerly expected not to.  Are you able to reproduce this?

Andreas, would you be able to provide -fdump-tree-vect-details information for
r196871 and r196872 to make it easier to debug the problem?

Thanks,
Bill


  parent reply	other threads:[~2013-05-02 15:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 14:48 [Bug target/56864] New: " schwab@linux-m68k.org
2013-04-07 14:56 ` [Bug target/56864] " dominiq at lps dot ens.fr
2013-04-07 15:26 ` schwab@linux-m68k.org
2013-04-07 15:31 ` dominiq at lps dot ens.fr
2013-04-07 16:30 ` schwab@linux-m68k.org
2013-04-07 17:33 ` dominiq at lps dot ens.fr
2013-04-08 11:16 ` rguenth at gcc dot gnu.org
2013-05-01 17:49 ` wschmidt at gcc dot gnu.org
2013-05-01 20:07 ` schwab@linux-m68k.org
2013-05-01 20:13 ` wschmidt at gcc dot gnu.org
2013-05-02 10:37 ` schwab@linux-m68k.org
2013-05-02 15:55 ` wschmidt at gcc dot gnu.org [this message]
2013-05-02 16:20 ` schwab@linux-m68k.org
2013-05-02 16:36 ` schwab@linux-m68k.org
2013-07-23 17:36 ` dje at gcc dot gnu.org
2013-10-25 12:52 ` rguenth at gcc dot gnu.org
2013-10-25 13:20 ` 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-56864-4-N2PRbFMeTh@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).