From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-470326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25808 invoked by alias); 11 Dec 2014 19:41:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 25768 invoked by uid 48); 11 Dec 2014 19:41:03 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: richard-gccbugzilla at metafoo dot co.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-64276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg01333.txt.bz2

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.