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/107412] Miss to fold LEN_{LOAD,STORE} when the specified length equal to vector length
Date: Mon, 05 Dec 2022 05:28:11 +0000	[thread overview]
Message-ID: <bug-107412-4-WU7PI2WnUm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107412-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:380d62c14c99d8df13b7a86660e7ee67d01ad827

commit r13-4488-g380d62c14c99d8df13b7a86660e7ee67d01ad827
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Dec 4 23:27:08 2022 -0600

    gimple-fold: Refine gimple_fold_partial_load_store_mem_ref [PR107412]

    Following Richard's review comments, this patch is to use
    untruncated type for the length used for IFN_LEN_{LOAD,STORE}
    instead of "unsigned int" for better robustness.  It also
    avoid to use to_constant and tree arithmetic for subtraction.

    Co-authored-by: Richard Sandiford  <richard.sandiford@arm.com>

            PR tree-optimization/107412

    gcc/ChangeLog:

            * gimple-fold.cc (gimple_fold_partial_load_store_mem_ref): Use
            untruncated type for the length, and avoid to_constant and tree
            arithmetic for subtraction.

      parent reply	other threads:[~2022-12-05  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  9:13 [Bug tree-optimization/107412] New: " linkw at gcc dot gnu.org
2022-10-26  9:15 ` [Bug tree-optimization/107412] " linkw at gcc dot gnu.org
2022-10-27 22:03 ` segher at gcc dot gnu.org
2022-10-31  6:39 ` linkw at gcc dot gnu.org
2022-11-07  8:17 ` cvs-commit at gcc dot gnu.org
2022-11-07  8:25 ` linkw at gcc dot gnu.org
2022-11-07  8:25 ` linkw at gcc dot gnu.org
2022-12-05  5:28 ` 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-107412-4-WU7PI2WnUm@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).