This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/52562] [C++11] Most type_info functions not noexcept
- From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Mar 2012 15:46:42 +0000
- Subject: [Bug libstdc++/52562] [C++11] Most type_info functions not noexcept
- Auto-submitted: auto-generated
- References: <bug-52562-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52562
--- Comment #8 from Daniel KrÃgler <daniel.kruegler at googlemail dot com> 2012-03-12 15:46:42 UTC ---
(In reply to comment #6)
There exists a compiler problem with noexcept and non-trivial destructor
declarations as described in bug 50043 and in bug 51295. This fix should
automagically ensure that std::type_infos destructor get's an assumed
noexcept(true) exception specification.
The additional library wording exists to ensure that independent of any implied
destructor exception specification of base classes or members of library
internals all destructors of library types needs to behave as noexcept. But
given the current definition of std::type_info there is no reason why an
explicit noexcept(true) specification should be required.