public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52562] [C++11] Most type_info functions not noexcept
Date: Mon, 12 Mar 2012 13:44:00 -0000	[thread overview]
Message-ID: <bug-52562-4-awoYdHk7zu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52562-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-03-12 13:43:35 UTC ---
Do I understand correctly that in N3291 the destructor lost the explicit
noexcept simply because of core/1123? In that case I think that in GCC we
should mark it temporarily noexcept and then remove it in mainline when
c++/50043 will be addressed (I mean to work on it over the next weeks).
4_7-branch will not change anymore.


  parent reply	other threads:[~2012-03-12 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 11:57 [Bug libstdc++/52562] New: " daniel.kruegler at googlemail dot com
2012-03-12 12:02 ` [Bug libstdc++/52562] " redi at gcc dot gnu.org
2012-03-12 12:54 ` paolo.carlini at oracle dot com
2012-03-12 13:16 ` paolo.carlini at oracle dot com
2012-03-12 13:44 ` paolo.carlini at oracle dot com [this message]
2012-03-12 13:50 ` paolo.carlini at oracle dot com
2012-03-12 14:07 ` daniel.kruegler at googlemail dot com
2012-03-12 15:03 ` paolo.carlini at oracle dot com
2012-03-12 15:13 ` paolo at gcc dot gnu.org
2012-03-12 15:47 ` daniel.kruegler at googlemail dot com
2012-03-12 16:09 ` paolo.carlini at oracle dot com
2012-04-22  8:04 ` paolo.carlini at oracle dot com

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-52562-4-awoYdHk7zu@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).