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 target/65660] [5 Regression] 252.eon regression on bdver2 with -Ofast
Date: Thu, 02 Apr 2015 12:02:00 -0000	[thread overview]
Message-ID: <bug-65660-4-16vkEiybfQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65660-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65660

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00053.html

C testcase:

void Set (float d, float *data)
{
  for (int i = 0; i < 8; i++)
    data[i] = d;
}

note that I didn't really verify it is that specific vectorization causing the
slowdown.  It just appears a lot in the diff.  As said we should recognize
that peeling for alignment is stupid here.  Will produce a patch for that as
well.


  parent reply	other threads:[~2015-04-02 12:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 10:19 [Bug target/65660] New: " rguenth at gcc dot gnu.org
2015-04-02 10:19 ` [Bug target/65660] " rguenth at gcc dot gnu.org
2015-04-02 10:29 ` trippels at gcc dot gnu.org
2015-04-02 10:31 ` trippels at gcc dot gnu.org
2015-04-02 10:58 ` rguenth at gcc dot gnu.org
2015-04-02 11:44 ` rguenth at gcc dot gnu.org
2015-04-02 12:02 ` rguenth at gcc dot gnu.org [this message]
2015-04-03 16:22 ` hubicka at gcc dot gnu.org
2015-04-03 16:28 ` hubicka at gcc dot gnu.org
2015-04-03 18:35 ` rguenther at suse dot de
2015-04-04 10:47 ` rguenth at gcc dot gnu.org
2015-04-05  0:27   ` Jan Hubicka
2015-04-04 11:38 ` rguenther at suse dot de
2015-04-05  0:27 ` hubicka at ucw dot cz
2015-04-07  7:26 ` rguenth at gcc dot gnu.org
2015-04-07  7:46 ` rguenth at gcc dot gnu.org
2015-04-07  9:35 ` rguenth at gcc dot gnu.org
2015-04-07 13:41 ` rguenth at gcc dot gnu.org
2015-04-08  5:53 ` hubicka at gcc dot gnu.org
2015-04-08  5:56 ` hubicka at gcc dot gnu.org
2015-04-08  7:26 ` rguenth at gcc dot gnu.org
2015-04-09  0:09 ` hubicka at gcc dot gnu.org
2015-04-09  7:30 ` rguenth at gcc dot gnu.org
2015-04-13  7:34 ` [Bug target/65660] [5/6 " rguenth at gcc dot gnu.org
2015-04-13  7:35 ` [Bug target/65660] [5 " rguenth at gcc dot gnu.org
2015-04-13  7:37 ` rguenth at gcc dot gnu.org
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16  9:13 ` 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-65660-4-16vkEiybfQ@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).