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/65456] powerpc64le autovectorized copy loop missed optimization
Date: Mon, 23 Mar 2015 13:50:00 -0000	[thread overview]
Message-ID: <bug-65456-4-o6BTdpaMNk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65456-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #10)
> I believe that the choice to scalarize is based on the vector cost model.

Hm, that would be interesting.  The applied patch changes the cost model to
favor the unaligned store on VSX.  Might be a place where it should be using
the cost model but perhaps isn't?  I'll look into it later this week.


  parent reply	other threads:[~2015-03-23 13:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  3:52 [Bug target/65456] New: " anton at samba dot org
2015-03-18  7:26 ` [Bug target/65456] " trippels at gcc dot gnu.org
2015-03-18  7:34 ` [Bug target/65456] [5 Regression] " trippels at gcc dot gnu.org
2015-03-18  7:50 ` [Bug target/65456] " trippels at gcc dot gnu.org
2015-03-18 11:29 ` rguenth at gcc dot gnu.org
2015-03-18 23:23 ` dje at gcc dot gnu.org
2015-03-19 19:25 ` msebor at gcc dot gnu.org
2015-03-19 22:52 ` anton at samba dot org
2015-03-20 14:47 ` wschmidt at gcc dot gnu.org
2015-03-22 16:59 ` wschmidt at gcc dot gnu.org
2015-03-23  4:21 ` dje at gcc dot gnu.org
2015-03-23 13:50 ` wschmidt at gcc dot gnu.org [this message]
2015-03-28  2:19 ` wschmidt at gcc dot gnu.org
2015-03-28 11:40 ` amodra at gmail dot com
2015-03-29 18:24 ` wschmidt at gcc dot gnu.org
2015-03-29 19:30 ` wschmidt at gcc dot gnu.org
2015-04-23  0:22 ` wschmidt at gcc dot gnu.org
2015-04-23 21:04 ` wschmidt at gcc dot gnu.org
2015-04-24 13:45 ` wschmidt at gcc dot gnu.org
2015-04-24 20:17 ` wschmidt at gcc dot gnu.org
2015-04-24 20:46 ` wschmidt at gcc dot gnu.org
2015-05-04 14:50 ` ro at gcc dot gnu.org
2015-05-04 14:51 ` ro at gcc dot gnu.org
2015-05-04 20:56 ` wschmidt at gcc dot gnu.org
2015-05-05 13:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-05-06 11:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-05-06 12:07 ` wschmidt 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-65456-4-o6BTdpaMNk@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).