public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33799] Return value's destructor not executed when a local variable's destructor throws
Date: Thu, 28 Nov 2013 11:18:00 -0000	[thread overview]
Message-ID: <bug-33799-4-A3Ef3XjEFU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-33799-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33799

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's now 2013 so the sensible thing to do is not return by value if your
destructor can throw.

FWIW Clang also behaves the same as G++ and Intel, and of course calls
std::terminate() in C++11 mode.


       reply	other threads:[~2013-11-28 11:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-33799-4@http.gcc.gnu.org/bugzilla/>
2013-11-28 11:18 ` redi at gcc dot gnu.org [this message]
2013-11-28 12:15 ` temporal at gmail dot com
2020-04-20  3:30 ` mm-nospam at outlook dot co.nz
2020-04-20  9:24 ` redi at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-07-23  6:52 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-01-06 14:31 ` jason at gcc dot gnu.org
2022-01-07  0:26 ` cvs-commit at gcc dot gnu.org
2022-02-01 22:51 ` jason at gcc dot gnu.org
2023-06-07  1:33 ` cvs-commit at gcc dot gnu.org
2023-11-02 20:01 ` cvs-commit at gcc dot gnu.org
2023-11-17  0:21 ` cvs-commit at gcc dot gnu.org
2023-11-17  0:21 ` cvs-commit at gcc dot gnu.org
2023-11-17  0:21 ` cvs-commit at gcc dot gnu.org
2023-11-17  0:21 ` cvs-commit at gcc dot gnu.org
2023-12-20 17:31 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:39 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:40 ` cvs-commit at gcc dot gnu.org
2007-10-17 11:31 [Bug c++/33799] New: " bitti at iki dot fi
2007-10-17 12:03 ` [Bug c++/33799] " rguenth at gcc dot gnu dot org
2007-10-17 12:21 ` bitti at iki dot fi
2007-10-17 17:07 ` jason at gcc dot gnu dot org
2008-09-19 12:14 ` bitti at iki dot fi

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-33799-4-A3Ef3XjEFU@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).