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/102216] [12 Regression] missed optimization causing Warray-bounds
Date: Tue, 23 Nov 2021 09:57:10 +0000	[thread overview]
Message-ID: <bug-102216-4-gINTjchkk7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102216-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:911b633803dcbb298c98777e29fd260834c0d04a

commit r12-5465-g911b633803dcbb298c98777e29fd260834c0d04a
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue Nov 23 01:08:55 2021 +0000

    Canonicalize &MEM[ssa_n, CST] to ssa_n p+ CST in fold_stmt_1

    This is a new version of the patch to fix PR 102216.
    Instead of doing the canonicalization inside forwprop, Richi
    mentioned we should do it inside fold_stmt_1 and that is what
    this patch does.

            PR tree-optimization/102216

    gcc/ChangeLog:

            * gimple-fold.c (fold_stmt_1): Add canonicalization
            of "&MEM[ssa_n, CST]" to "ssa_n p+ CST", note this
            can only be done if !in_place.

    gcc/testsuite/ChangeLog:

            * g++.dg/tree-ssa/pr102216-1.C: New test.
            * g++.dg/tree-ssa/pr102216-2.C: New test.

  parent reply	other threads:[~2021-11-23  9:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 10:14 [Bug tree-optimization/102216] New: False positive warray-bounds with -O2 vries at gcc dot gnu.org
2021-09-06 10:45 ` [Bug tree-optimization/102216] " pinskia at gcc dot gnu.org
2021-09-06 20:46 ` pinskia at gcc dot gnu.org
2021-09-07  1:32 ` [Bug tree-optimization/102216] [12 Regression] missed optimization causing Warray-bounds pinskia at gcc dot gnu.org
2021-09-07  1:47 ` pinskia at gcc dot gnu.org
2021-09-07  6:31 ` pinskia at gcc dot gnu.org
2021-09-07  7:21 ` pinskia at gcc dot gnu.org
2021-09-07 18:50 ` pinskia at gcc dot gnu.org
2021-09-07 21:37 ` pinskia at gcc dot gnu.org
2021-09-15 16:40 ` msebor at gcc dot gnu.org
2021-09-15 19:19 ` pinskia at gcc dot gnu.org
2021-10-27  9:28 ` pinskia at gcc dot gnu.org
2021-11-23  0:50 ` pinskia at gcc dot gnu.org
2021-11-23  1:31 ` pinskia at gcc dot gnu.org
2021-11-23  5:30 ` pinskia at gcc dot gnu.org
2021-11-23  8:45 ` pinskia at gcc dot gnu.org
2021-11-23  9:57 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-23 10:01 ` pinskia 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-102216-4-gINTjchkk7@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).