From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17110 invoked by alias); 1 Feb 2013 08:42:21 -0000 Received: (qmail 17040 invoked by uid 48); 1 Feb 2013 08:41:59 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/56166] std::string::clear() can throw despite being marked noexcept Date: Fri, 01 Feb 2013 08:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2013-02/txt/msg00015.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56166 --- Comment #5 from Paolo Carlini 2013-02-01 08:41:59 UTC --- 4.9, yes. Of course wrt the C++11 requirements the current implementation is non conforming for many other reasons (reference counting is out ruled) + there are long standing bugs (in partixular alignment related and related to the shared zero rep for some targets). It goes without saying that when ext/vstring is promoted it also gets automatically all the iostream overloads, etc, and further improvements are definitely welcome. That said, for sure I don't mean to unconditionally oppose fixes to the current implementation, eh Jon's idea seems fine to me in principle, if only he could prototype it, would be great, my point was that it doesn't seem to make much sense doing a *lot* of that *now*.