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 c++/101072] [11/12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 since r11-5681-gd9288bd28e24c755
Date: Wed, 07 Jul 2021 22:50:14 +0000	[thread overview]
Message-ID: <bug-101072-4-KPSbXhO6EG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101072-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:79663c962588e8c033ff39be39e938e2cc866e12

commit r11-8705-g79663c962588e8c033ff39be39e938e2cc866e12
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Jul 7 17:57:40 2021 -0400

    Revert "c++: Improve init handling"

    Apparently looking through these codes means that in a template, we end up
    feeding a TARGET_EXPR to fold_non_dependent_expr, which should never
    happen.  This is a broader issue, but for now let's just revert the change.

    This reverts commit d9288bd28e24c755a7216311ee5247e7c88270a6.

            PR c++/101072

    gcc/cp/ChangeLog:

            * decl.c (check_initializer): Don't look through STMT_EXPR and
            BIND_EXPR.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/constexpr-empty14.C: Add -fno-elide-constructors.

  parent reply	other threads:[~2021-07-07 22:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 17:23 [Bug c++/101072] New: [11/12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 gscfq@t-online.de
2021-06-15  7:22 ` [Bug c++/101072] [11/12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 since r11-5681-gd9288bd28e24c755 marxin at gcc dot gnu.org
2021-06-15  7:53 ` rguenth at gcc dot gnu.org
2021-07-07 21:38 ` jason at gcc dot gnu.org
2021-07-07 22:50 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-07 22:50 ` [Bug c++/101072] [12 " jason at gcc dot gnu.org
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2021-12-28 23:48 ` pinskia at gcc dot gnu.org
2022-01-23  3:19 ` cvs-commit at gcc dot gnu.org
2022-01-23 22:33 ` jason at gcc dot gnu.org
2022-01-26 19:27 ` cvs-commit 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-101072-4-KPSbXhO6EG@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).