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/98674] [10/11 Regression] vectorizer failed for compilation time alias
Date: Thu, 14 Jan 2021 15:14:13 +0000	[thread overview]
Message-ID: <bug-98674-4-M2w7G2S0Ur@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98674-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:2182274f510c180ea92a4f826a0f6cf5f1f55b66

commit r11-6670-g2182274f510c180ea92a4f826a0f6cf5f1f55b66
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Jan 14 14:08:41 2021 +0100

    tree-optimization/98674 - improve dependence analysis

    This improves dependence analysis on refs that access the same
    array but with different typed but same sized accesses.  That's
    obviously safe for the case of types that cannot have any
    access function based off them.  For the testcase this is
    signed short vs. unsigned short.

    2021-01-14  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/98674
            * tree-data-ref.c (base_supports_access_fn_components_p): New.
            (initialize_data_dependence_relation): For two bases without
            possible access fns resort to type size equality when determining
            shape compatibility.

            * gcc.dg/vect/pr98674.c: New testcase.

  parent reply	other threads:[~2021-01-14 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 10:19 [Bug tree-optimization/98674] New: [10/11] Regression " crazylht at gmail dot com
2021-01-14 10:55 ` [Bug tree-optimization/98674] " rguenth at gcc dot gnu.org
2021-01-14 12:50 ` rguenth at gcc dot gnu.org
2021-01-14 13:19 ` [Bug tree-optimization/98674] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-14 13:26 ` rguenth at gcc dot gnu.org
2021-01-14 13:27 ` rsandifo at gcc dot gnu.org
2021-01-14 13:38 ` rguenther at suse dot de
2021-01-14 15:14 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-14 15:14 ` [Bug tree-optimization/98674] [10 " rguenth at gcc dot gnu.org
2021-01-14 15:14 ` rguenth at gcc dot gnu.org
2021-01-15  2:49 ` crazylht at gmail dot com
2021-01-15  7:56 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07  9:22 ` 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-98674-4-M2w7G2S0Ur@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).