public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ctice at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66917] [4.9/5 regression] ARM: NEON: memcpy compiles to vst1 with incorrect alignment
Date: Thu, 24 Sep 2015 20:57:00 -0000	[thread overview]
Message-ID: <bug-66917-4-2XBkTsjLDZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66917-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from ctice at gcc dot gnu.org ---
Author: ctice
Date: Thu Sep 24 20:56:29 2015
New Revision: 228099

URL: https://gcc.gnu.org/viewcvs?rev=228099&root=gcc&view=rev
Log:
Backport r226487 from GCC FSF mainline:

r226487 | rguenth | 2015-08-03 00:13:36 -0700 (Mon, 03 Aug 2015) | 15 lines

2015-08-03  Richard Biener  <rguenther@suse.de>

        PR tree-optimization/66917
        * tree-vectorizer.h (struct dataref_aux): Add base_element_aligned
        field.
        (DR_VECT_AUX): New macro.
        (set_dr_misalignment): Adjust.
        (dr_misalignment): Likewise.
        * tree-vect-data-refs.c (vect_compute_data_ref_alignment):
        Compute whether the base is at least element aligned.
        * tree-vect-stmts.c (ensure_base_align): Adjust.
        (vectorizable_store): If the base is not element aligned
        preserve alignment of the original access if misalignment is unknown.
        (vectorizable_load): Likewise.



Modified:
    branches/google/gcc-4_9-mobile/gcc/tree-vect-data-refs.c
    branches/google/gcc-4_9-mobile/gcc/tree-vect-stmts.c
    branches/google/gcc-4_9-mobile/gcc/tree-vectorizer.h


  parent reply	other threads:[~2015-09-24 20:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-66917-4@http.gcc.gnu.org/bugzilla/>
2015-07-19 18:28 ` [Bug target/66917] ARM: NEON: memcpy compiles to vld1 and " mikpelinux at gmail dot com
2015-07-29  8:21 ` [Bug tree-optimization/66917] " ramana at gcc dot gnu.org
2015-07-29  8:23 ` [Bug tree-optimization/66917] [4.9/5/6 regression] " ramana at gcc dot gnu.org
2015-07-29 14:03 ` ktkachov at gcc dot gnu.org
2015-07-29 14:37 ` rguenth at gcc dot gnu.org
2015-07-29 14:41 ` ktkachov at gcc dot gnu.org
2015-07-29 14:47 ` ktkachov at gcc dot gnu.org
2015-07-30  7:20 ` [Bug tree-optimization/66917] [4.9/5/6 regression] ARM: NEON: memcpy compiles to vst1 with incorrect alignment due to SRA rguenth at gcc dot gnu.org
2015-07-30  7:43 ` [Bug target/66917] " rguenth at gcc dot gnu.org
2015-07-30  7:48 ` rguenth at gcc dot gnu.org
2015-07-30 14:11 ` [Bug tree-optimization/66917] " rearnsha at gcc dot gnu.org
2015-07-30 14:39 ` rguenther at suse dot de
2015-07-30 14:41 ` rguenth at gcc dot gnu.org
2015-07-31  9:20 ` rguenth at gcc dot gnu.org
2015-07-31  9:23 ` ktkachov at gcc dot gnu.org
2015-07-31 13:21 ` ktkachov at gcc dot gnu.org
2015-08-03  7:14 ` [Bug tree-optimization/66917] [4.9/5 regression] ARM: NEON: memcpy compiles to vst1 with incorrect alignment rguenth at gcc dot gnu.org
2015-08-03  7:14 ` rguenth at gcc dot gnu.org
2015-09-24 20:57 ` ctice at gcc dot gnu.org [this message]
2015-09-28 10:46 ` 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-66917-4-2XBkTsjLDZ@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).