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++/113347] [12/13 Regression] ICE during gimplification building TVM since r13-8079-gd237e7b291ff52
Date: Wed, 24 Jan 2024 19:39:12 +0000	[thread overview]
Message-ID: <bug-113347-4-BKiWFcOhvU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113347-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:713fbaff8b17a01d3b72110f89112851ed43a90a

commit r13-8249-g713fbaff8b17a01d3b72110f89112851ed43a90a
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Jan 23 15:41:09 2024 -0500

    c++: throwing cleanup after return [PR113347]

    Here we were assuming that current_retval_sentinel would be set if we have
    seen a throwing cleanup, but that's not the case if the cleanup is after
all
    returns.

    This change isn't needed on trunk, where current_retval_sentinel is set for
    all NRV functions.

            PR c++/113347

    gcc/cp/ChangeLog:

            * semantics.cc (finalize_nrv_r): Handle null
            current_retval_sentinel.

    gcc/testsuite/ChangeLog:

            * g++.dg/eh/return3.C: New test.

  parent reply	other threads:[~2024-01-24 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12  7:17 [Bug c++/113347] New: ICE during gimplification building TVM rguenth at gcc dot gnu.org
2024-01-12  7:17 ` [Bug c++/113347] " rguenth at gcc dot gnu.org
2024-01-12  7:18 ` rguenth at gcc dot gnu.org
2024-01-12  7:20 ` [Bug c++/113347] [13 Regression] " rguenth at gcc dot gnu.org
2024-01-12  8:10 ` fabian@ritter-vogt.de
2024-01-12  8:24 ` [Bug c++/113347] [13 Regression] ICE during gimplification building TVM since r13-8079-gd237e7b291ff52 rguenth at gcc dot gnu.org
2024-01-12  8:28 ` [Bug c++/113347] [12/13 " rguenth at gcc dot gnu.org
2024-01-15  7:33 ` rguenth at gcc dot gnu.org
2024-01-15 19:08 ` mpolacek at gcc dot gnu.org
2024-01-18 19:16 ` mpolacek at gcc dot gnu.org
2024-01-22 22:43 ` pinskia at gcc dot gnu.org
2024-01-23 20:28 ` jason at gcc dot gnu.org
2024-01-24 19:39 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-24 19:40 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:42 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:43 ` jason 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-113347-4-BKiWFcOhvU@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).