public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/21772] exception safety testing
Date: Thu, 04 Mar 2010 12:00:00 -0000 [thread overview]
Message-ID: <20100304115947.1518.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21772-365@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from paolo dot carlini at oracle dot com 2010-03-04 11:59 -------
I'm analyzing the remaining xfails. About generation_prohibited, for vector and
deque, I see the tests failing only on the two forms of erase. But in that
case, the Standard (*) says that: "Throws: Nothing unless an exception is
thrown by the copy constructor or assignment operator of T.". Thus, I don't
think we have a bug. Benjamin, do you have a contrary opinion? Otherwise I'm
tempted to take out those erase from generation_prohibited for deque and
vector.
(*) C++1x as of n3035 is exactly like C++03 here. Of course for now we are not
taking into account any subtlety with throwing move constructor and assignment,
still being finalized by the Committee. In any case in our library we are not
testing yet with moveable types.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21772
next prev parent reply other threads:[~2010-03-04 12:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21772-365@http.gcc.gnu.org/bugzilla/>
2007-05-21 8:27 ` [Bug libstdc++/21772] exception safety testing allocator pcarlini at suse dot de
2007-05-21 14:58 ` bkoz at gcc dot gnu dot org
2007-05-21 16:16 ` dave at boost-consulting dot com
2007-05-21 17:13 ` pcarlini at suse dot de
2007-05-27 23:07 ` dave at boost-consulting dot com
2009-12-16 3:34 ` bkoz at gcc dot gnu dot org
2009-12-16 3:34 ` [Bug libstdc++/21772] exception safety testing bkoz at gcc dot gnu dot org
2009-12-16 3:36 ` bkoz at gcc dot gnu dot org
2009-12-16 5:17 ` bkoz at gcc dot gnu dot org
2009-12-16 10:14 ` paolo dot carlini at oracle dot com
2009-12-16 11:14 ` jwakely dot gcc at gmail dot com
2009-12-17 8:18 ` bkoz at gcc dot gnu dot org
2009-12-17 9:37 ` bkoz at gcc dot gnu dot org
2009-12-17 9:58 ` paolo dot carlini at oracle dot com
2010-01-01 3:39 ` bkoz at gcc dot gnu dot org
2010-01-01 3:55 ` bkoz at gcc dot gnu dot org
2010-01-01 10:14 ` paolo dot carlini at oracle dot com
2010-01-01 10:46 ` paolo dot carlini at oracle dot com
2010-01-01 11:03 ` paolo dot carlini at oracle dot com
2010-02-19 10:49 ` paolo dot carlini at oracle dot com
2010-03-04 12:00 ` paolo dot carlini at oracle dot com [this message]
[not found] <bug-21772-4@http.gcc.gnu.org/bugzilla/>
2023-05-16 19:41 ` pinskia 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=20100304115947.1518.qmail@sourceware.org \
--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).