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++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Thu, 29 Sep 2022 17:52:27 +0000	[thread overview]
Message-ID: <bug-93046-4-LHhuNSYxQi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:bbdb5612f6661f2c64b0c0f1d2291cb59fde2b40

commit r13-2964-gbbdb5612f6661f2c64b0c0f1d2291cb59fde2b40
Author: Jason Merrill <jason@redhat.com>
Date:   Fri Sep 23 09:07:22 2022 -0400

    c++: fix class-valued ?: extension

    When the gimplifier encounters the same TARGET_EXPR twice, it evaluates
    TARGET_EXPR_INITIAL the first time and clears it so that the later
    evaluation is just the temporary.  With this testcase, using the extension
    to treat an omitted middle operand as repeating the first operand, that led
    to doing a bitwise copy of the S(1) temporary on return rather than
properly
    calling the copy constructor.

    We can't use S(1) to initialize the return value here anyway, because we
    need to materialize it into a temporary so we can convert it to bool and
    determine which arm we're evaluating.  So let's just treat the middle
    operand as an xvalue.

            PR c++/93046

    gcc/cp/ChangeLog:

            * call.cc (build_conditional_expr): For a?:c extension, treat
            a reused class prvalue as an xvalue.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/cond4.C: Add runtime test.

           reply	other threads:[~2022-09-29 17:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-93046-4@http.gcc.gnu.org/bugzilla/>]

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-93046-4-LHhuNSYxQi@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).