From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-322452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 16546 invoked by alias); 23 Jun 2010 14:35:19 -0000
Received: (qmail 16487 invoked by uid 48); 23 Jun 2010 14:35:06 -0000
Date: Wed, 23 Jun 2010 14:35:00 -0000
Subject: [Bug libstdc++/44647]  New: std::nothrow and std::bad_alloc are coupled
X-Bugzilla-Reason: CC
Message-ID: <bug-44647-16781@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "sebastian dot huber at embedded-brains dot de" <gcc-bugzilla@gcc.gnu.org>
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
X-SW-Source: 2010-06/txt/msg02287.txt.bz2

The definitions of std::nothrow, __new_handler and std::bad_alloc are in the
same file.  This is bad since the std::bad_alloc definition pulls in the
exception support.  The std::bad_alloc definitions should be placed into a
separate file.


-- 
           Summary: std::nothrow and std::bad_alloc are coupled
           Product: gcc
           Version: 4.4.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sebastian dot huber at embedded-brains dot de


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