public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97043] latent wrong-code with SLP vectorization
Date: Fri, 18 Feb 2022 08:21:11 +0000	[thread overview]
Message-ID: <bug-97043-4-pr4eZex5WV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97043-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:e75e5d2c41d294c4da4adfe610204ce5d97c3a4e

commit r9-9959-ge75e5d2c41d294c4da4adfe610204ce5d97c3a4e
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Sep 14 11:25:04 2020 +0200

    tree-optimization/97043 - fix latent wrong-code with SLP vectorization

    When the unrolling decision comes late and would have prevented
    eliding a SLP load permutation we can end up generating aligned
    loads when the load is in fact unaligned.  Most of the time
    alignment analysis figures out the load is in fact unaligned
    but that cannot be relied upon.

    The following removes the SLP load permutation eliding based on
    the still premature vectorization factor.

    2020-09-14  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/97043
            * tree-vect-slp.c (vect_analyze_slp_instance): Do not
            elide a load permutation if the current vectorization
            factor is one.

    (cherry picked from commit e93428a8b056aed83a7678d4dc8272131ab671ba)

      parent reply	other threads:[~2022-02-18  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  9:01 [Bug tree-optimization/97043] New: " rguenth at gcc dot gnu.org
2020-09-14  9:16 ` [Bug tree-optimization/97043] " rguenth at gcc dot gnu.org
2020-09-14  9:30 ` rguenth at gcc dot gnu.org
2020-09-14 13:22 ` cvs-commit at gcc dot gnu.org
2020-10-06 12:20 ` rguenth at gcc dot gnu.org
2021-02-03  8:26 ` rguenth at gcc dot gnu.org
2021-02-03  8:27 ` rguenth at gcc dot gnu.org
2021-02-08 10:43 ` rguenth at gcc dot gnu.org
2022-02-18  8:21 ` cvs-commit at gcc dot gnu.org [this message]

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-97043-4-pr4eZex5WV@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).