public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/21772] exception safety testing
Date: Thu, 17 Dec 2009 09:37:00 -0000 [thread overview]
Message-ID: <20091217093731.15684.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21772-365@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from bkoz at gcc dot gnu dot org 2009-12-17 09:37 -------
Subject: Bug 21772
Author: bkoz
Date: Thu Dec 17 09:37:16 2009
New Revision: 155306
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155306
Log:
2009-12-16 Benjamin Kosnik <bkoz@redhat.com>
PR libstdc++/21772 part 2
* doc/xml/manual/test.xml: Add documentation about testing details.
* testsuite/util/exception/safety.h: New. Functor objects for
testing C++0x container classes.
* testsuite/util/testsuite_container_traits.h: Add traits.
* testsuite/23_containers/list/requirements/exception/
basic.cc: New.
generation_prohibited.cc: New.
propagation_consistent.cc: New.
Added:
trunk/libstdc++-v3/testsuite/23_containers/list/requirements/exception/
trunk/libstdc++-v3/testsuite/23_containers/list/requirements/exception/basic.cc
trunk/libstdc++-v3/testsuite/23_containers/list/requirements/exception/generation_prohibited.cc
trunk/libstdc++-v3/testsuite/23_containers/list/requirements/exception/propagation_consistent.cc
trunk/libstdc++-v3/testsuite/util/exception/
trunk/libstdc++-v3/testsuite/util/exception/safety.h
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/doc/xml/manual/test.xml
trunk/libstdc++-v3/testsuite/util/testsuite_container_traits.h
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21772
next prev parent reply other threads:[~2009-12-17 9:37 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 ` [Bug libstdc++/21772] exception safety testing bkoz at gcc dot gnu dot org
2009-12-16 3:34 ` [Bug libstdc++/21772] exception safety testing allocator bkoz at gcc dot gnu dot org
2009-12-16 3:36 ` [Bug libstdc++/21772] exception safety testing 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 [this message]
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
[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=20091217093731.15684.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).