public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r9-9817] middle-end/101824 - properly handle volatiles in nested fn lowering
Date: Mon,  8 Nov 2021 14:07:35 +0000 (GMT)	[thread overview]
Message-ID: <20211108140735.377723858406@sourceware.org> (raw)

https://gcc.gnu.org/g:8dec0ae6200ae8c56dbeef5ff9acd2214282de67

commit r9-9817-g8dec0ae6200ae8c56dbeef5ff9acd2214282de67
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Aug 9 10:19:10 2021 +0200

    middle-end/101824 - properly handle volatiles in nested fn lowering
    
    When we build the COMPONENT_REF of a formerly volatile local off
    the FRAME decl we have to make sure to mark the COMPONENT_REF
    as TREE_THIS_VOLATILE.  While the GIMPLE operand scanner looks
    at the FIELD_DECL this is not how volatile GENERIC refs work.
    
    2021-08-09  Richard Biener  <rguenther@suse.de>
    
            PR middle-end/101824
            * tree-nested.c (get_frame_field): Mark the COMPONENT_REF as
            volatile in case the variable was.
    
            * gcc.dg/tree-ssa/pr101824.c: New testcase.
    
    (cherry picked from commit bb169406cdc9e044eaec500dd742c2fed40f5488)

Diff:
---
 gcc/testsuite/gcc.dg/tree-ssa/pr101824.c | 19 +++++++++++++++++++
 gcc/tree-nested.c                        |  1 +
 2 files changed, 20 insertions(+)

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr101824.c b/gcc/testsuite/gcc.dg/tree-ssa/pr101824.c
new file mode 100644
index 00000000000..d5987e14360
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/tree-ssa/pr101824.c
@@ -0,0 +1,19 @@
+/* { dg-do compile } */
+/* { dg-options "-O3 -fdump-tree-pcom-details -fdump-tree-optimized" } */
+
+int main()
+{
+  volatile int y;
+  void bar()
+    {
+      __builtin_printf ("%d", y);
+    }
+  while (y)
+    ;
+  return 0;
+}
+
+/* Make sure the load from y is correctly interpreted as volatile, even
+   when going through FRAME.  */
+/* { dg-final { scan-tree-dump-not "Executing predictive commoning" "pcom" } } */
+/* { dg-final { scan-tree-dump " ={v} FRAME" "optimized" } } */
diff --git a/gcc/tree-nested.c b/gcc/tree-nested.c
index dc0cfe27142..a2ae3aefe4a 100644
--- a/gcc/tree-nested.c
+++ b/gcc/tree-nested.c
@@ -923,6 +923,7 @@ get_frame_field (struct nesting_info *info, tree target_context,
     }
 
   x = build3 (COMPONENT_REF, TREE_TYPE (field), x, field, NULL_TREE);
+  TREE_THIS_VOLATILE (x) = TREE_THIS_VOLATILE (field);
   return x;
 }


                 reply	other threads:[~2021-11-08 14:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211108140735.377723858406@sourceware.org \
    --to=rguenth@gcc.gnu.org \
    --cc=gcc-cvs@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).