From: Marek Polacek <polacek@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to tweak cp_fully_fold (PR c++/84590)
Date: Thu, 01 Mar 2018 21:38:00 -0000 [thread overview]
Message-ID: <20180301213836.GF16833@redhat.com> (raw)
In-Reply-To: <CADzB+2=0bU0iRb8+O5Jehvjp72-S_ghGNUnywPV1FWkU3JnYHQ@mail.gmail.com>
On Thu, Mar 01, 2018 at 02:29:47PM -0500, Jason Merrill wrote:
> I think this should happen in the block with maybe_constant_value;
> cp_fold_rvalue doesn't do this.
This, then:
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2018-03-01 Marek Polacek <polacek@redhat.com>
PR c++/84590
* cp-gimplify.c (cp_fully_fold): Unwrap TARGET_EXPR or a CONSTRUCTOR
wrapped in VIEW_CONVERT_EXPR.
* c-c++-common/ubsan/shift-11.c: New test.
diff --git gcc/cp/cp-gimplify.c gcc/cp/cp-gimplify.c
index 55a9d278dbe..0ddd435454c 100644
--- gcc/cp/cp-gimplify.c
+++ gcc/cp/cp-gimplify.c
@@ -2037,7 +2037,17 @@ cp_fully_fold (tree x)
/* FIXME cp_fold ought to be a superset of maybe_constant_value so we don't
have to call both. */
if (cxx_dialect >= cxx11)
- x = maybe_constant_value (x);
+ {
+ x = maybe_constant_value (x);
+ /* Sometimes we are given a CONSTRUCTOR but the call above wraps it into
+ a TARGET_EXPR; undo that here. */
+ if (TREE_CODE (x) == TARGET_EXPR)
+ x = TARGET_EXPR_INITIAL (x);
+ else if (TREE_CODE (x) == VIEW_CONVERT_EXPR
+ && TREE_CODE (TREE_OPERAND (x, 0)) == CONSTRUCTOR
+ && TREE_TYPE (TREE_OPERAND (x, 0)) == TREE_TYPE (x))
+ x = TREE_OPERAND (x, 0);
+ }
return cp_fold_rvalue (x);
}
diff --git gcc/testsuite/c-c++-common/ubsan/shift-11.c gcc/testsuite/c-c++-common/ubsan/shift-11.c
index e69de29bb2d..03a72e217a2 100644
--- gcc/testsuite/c-c++-common/ubsan/shift-11.c
+++ gcc/testsuite/c-c++-common/ubsan/shift-11.c
@@ -0,0 +1,13 @@
+/* PR c++/84590 */
+/* { dg-do compile } */
+/* { dg-options "-fsanitize=shift" } */
+
+struct S {
+ int b;
+};
+
+void
+fn (void)
+{
+ struct S c1 = { 1 << -1 }; /* { dg-warning "left shift" } */
+}
Marek
next prev parent reply other threads:[~2018-03-01 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 19:12 Marek Polacek
2018-03-01 19:30 ` Jason Merrill
2018-03-01 21:38 ` Marek Polacek [this message]
2018-03-02 0:59 ` Jason Merrill
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=20180301213836.GF16833@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).