public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/58776] [4.9 Regression]: gcc.dg/tree-ssa/gen-vect-32.c scan-tree-dump-times vect "vectorized 1 loops" 1
Date: Fri, 17 Jan 2014 10:24:00 -0000	[thread overview]
Message-ID: <bug-58776-4-QDnjSCImb7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58776-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 31869
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31869&action=edit
gcc49-pr58776.patch

For vectorization at -O2 the default now is the cheap cost model which doesn't
allow peeling for alignment, so what you get is IMHO desirable.

I think we should just add -fno-vect-cost-model to this test.


  parent reply	other threads:[~2014-01-17 10:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  3:46 [Bug tree-optimization/58776] New: " hp at gcc dot gnu.org
2013-10-18  3:56 ` [Bug tree-optimization/58776] " hp at gcc dot gnu.org
2013-10-18  3:57 ` hp at gcc dot gnu.org
2013-10-18  8:16 ` rguenth at gcc dot gnu.org
2013-11-05 15:06 ` rguenth at gcc dot gnu.org
2013-11-05 23:37 ` hp at gcc dot gnu.org
2013-11-19 10:21 ` rguenth at gcc dot gnu.org
2014-01-17 10:24 ` jakub at gcc dot gnu.org [this message]
2014-01-17 14:44 ` [Bug testsuite/58776] " jakub at gcc dot gnu.org
2014-01-17 14:54 ` jakub 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-58776-4-QDnjSCImb7@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).