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 libstdc++/64276] would be better to use __cpp_exceptions rather than __EXCEPTIONS to determine whether exceptions are available
Date: Fri, 12 Dec 2014 15:59:00 -0000 [thread overview]
Message-ID: <bug-64276-4-IQf3aTTc9h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64276-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64276
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Dec 12 15:58:49 2014
New Revision: 218679
URL: https://gcc.gnu.org/viewcvs?rev=218679&root=gcc&view=rev
Log:
PR libstdc++/64276
* doc/doxygen/user.cfg.in: Define __cpp_exceptions and __cpp_rtti.
* doc/html/manual/using_exceptions.html: Regenerate.
* doc/xml/manual/using_exceptions.xml: Use SD-6 feature-testing
macros, __cpp_exceptions and __cpp_rtti, instead of __EXCEPTIONS and
__GXX_RTTI.
* include/bits/c++config: Likewise.
* include/bits/locale_classes.tcc: Likewise.
* include/bits/shared_ptr.h: Likewise.
* include/bits/shared_ptr_base.h: Likewise.
* include/debug/formatter.h: Likewise.
* include/experimental/any: Likewise.
* include/ext/rope: Likewise.
* include/ext/ropeimpl.h: Likewise.
* include/std/functional: Likewise.
* include/tr1/functional: Likewise.
* include/tr1/shared_ptr.h: Likewise.
* libsupc++/eh_call.cc: Likewise.
* libsupc++/eh_personality.cc: Likewise.
* libsupc++/exception_defines.h: Likewise.
* libsupc++/exception_ptr.h: Likewise.
* libsupc++/guard.cc: Likewise.
* libsupc++/pbase_type_info.cc: Likewise.
* libsupc++/pointer_type_info.cc: Likewise.
* libsupc++/vterminate.cc: Likewise.
* src/c++11/thread.cc: Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/doc/doxygen/user.cfg.in
trunk/libstdc++-v3/doc/html/manual/using_exceptions.html
trunk/libstdc++-v3/doc/xml/manual/using_exceptions.xml
trunk/libstdc++-v3/include/bits/c++config
trunk/libstdc++-v3/include/bits/locale_classes.tcc
trunk/libstdc++-v3/include/bits/shared_ptr.h
trunk/libstdc++-v3/include/bits/shared_ptr_base.h
trunk/libstdc++-v3/include/debug/formatter.h
trunk/libstdc++-v3/include/experimental/any
trunk/libstdc++-v3/include/ext/rope
trunk/libstdc++-v3/include/ext/ropeimpl.h
trunk/libstdc++-v3/include/std/functional
trunk/libstdc++-v3/include/tr1/functional
trunk/libstdc++-v3/include/tr1/shared_ptr.h
trunk/libstdc++-v3/libsupc++/eh_call.cc
trunk/libstdc++-v3/libsupc++/eh_personality.cc
trunk/libstdc++-v3/libsupc++/exception_defines.h
trunk/libstdc++-v3/libsupc++/exception_ptr.h
trunk/libstdc++-v3/libsupc++/guard.cc
trunk/libstdc++-v3/libsupc++/pbase_type_info.cc
trunk/libstdc++-v3/libsupc++/pointer_type_info.cc
trunk/libstdc++-v3/libsupc++/vterminate.cc
trunk/libstdc++-v3/src/c++11/thread.cc
next prev parent reply other threads:[~2014-12-12 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 19:41 [Bug libstdc++/64276] New: " richard-gccbugzilla at metafoo dot co.uk
2014-12-12 3:50 ` [Bug libstdc++/64276] " pinskia at gcc dot gnu.org
2014-12-12 7:52 ` jakub at gcc dot gnu.org
2014-12-12 11:26 ` redi at gcc dot gnu.org
2014-12-12 15:59 ` redi at gcc dot gnu.org [this message]
2014-12-12 16:00 ` redi 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-64276-4-IQf3aTTc9h@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).