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/102714] [11/12 Regression] A volatile-related problem cased by ipa inline pass
Date: Wed, 13 Oct 2021 09:26:43 +0000	[thread overview]
Message-ID: <bug-102714-4-NbMbzwQE2f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102714-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:23cd18c60c8188e3d68eda721cdb739199e85e5b

commit r12-4366-g23cd18c60c8188e3d68eda721cdb739199e85e5b
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Oct 13 09:13:36 2021 +0200

    ipa/102714 - IPA SRA eliding volatile

    The following fixes the volatileness check of IPA SRA which was
    looking at the innermost reference when checking TREE_THIS_VOLATILE
    but the reference to check is the outermost one.

    2021-10-13  Richard Biener  <rguenther@suse.de>

            PR ipa/102714
            * ipa-sra.c (ptr_parm_has_nonarg_uses): Fix volatileness
            check.

            * gcc.dg/ipa/pr102714.c: New testcase.

  parent reply	other threads:[~2021-10-13  9:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 17:17 [Bug tree-optimization/102714] New: " duan.db at linux dot alibaba.com
2021-10-13  2:11 ` [Bug tree-optimization/102714] " jefflexu at linux dot alibaba.com
2021-10-13  7:09 ` [Bug tree-optimization/102714] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-10-13  9:26 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-13  9:30 ` [Bug tree-optimization/102714] [11 " rguenth at gcc dot gnu.org
2021-10-13 10:43 ` duan.db at linux dot alibaba.com
2021-10-29  2:12 ` duan.db at linux dot alibaba.com
2021-10-29  6:55 ` rguenth at gcc dot gnu.org
2021-10-29  7:03 ` [Bug tree-optimization/102714] [10/11 " rguenth at gcc dot gnu.org
2021-10-29  8:06 ` duan.db at linux dot alibaba.com
2021-11-03 13:09 ` cvs-commit at gcc dot gnu.org
2021-11-05  1:53 ` [Bug tree-optimization/102714] [10 " duan.db at linux dot alibaba.com
2021-11-05  7:08 ` rguenther at suse dot de
2021-11-09 13:06 ` cvs-commit at gcc dot gnu.org
2021-11-09 13:06 ` 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-102714-4-NbMbzwQE2f@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).