public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/64276] New: would be better to use __cpp_exceptions rather than __EXCEPTIONS to determine whether exceptions are available Date: Thu, 11 Dec 2014 19:41:00 -0000 [thread overview] Message-ID: <bug-64276-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64276 Bug ID: 64276 Summary: would be better to use __cpp_exceptions rather than __EXCEPTIONS to determine whether exceptions are available Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: richard-gccbugzilla at metafoo dot co.uk CC: redi at gcc dot gnu.org libstdc++ uses __EXCEPTIONS to determine wither exceptions are available, and uses __GXX_RTTI to determine if RTTI is available. __EXCEPTIONS is ambiguous; it can mean either "generate cleanups on exception unwind paths" or "allow C++ exception handling syntax", and some compilers allow these flags to be set independently. It would be more portable (and would set a better example) to use __cpp_exceptions and __cpp_rtti rather than these macros, now that GCC supports them.
next reply other threads:[~2014-12-11 19:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-11 19:41 richard-gccbugzilla at metafoo dot co.uk [this message] 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 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@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: linkBe 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).