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++/28457] ext/pb_ds/regression/tree_data_map_rand.cc fails with a particular random seed. Date: Fri, 06 Oct 2006 10:41:00 -0000 [thread overview] Message-ID: <20061006104106.14488.qmail@sourceware.org> (raw) In-Reply-To: <bug-28457-3264@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from bkoz at gcc dot gnu dot org 2006-10-06 10:41 ------- try again. the thing about (now) throw_allocator is that if some of the testcases have allocated memory and then an exception is thrown, the "leaked" memory is actually testsuite-type temporaries that should have been deleted. So, this could be a false herring. Anyway. I think the the only remaining pb_ds regressions that show up regularly are the priority_queue dijkstra tests on powerpc. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28457
next prev parent reply other threads:[~2006-10-06 10:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-22 1:55 [Bug libstdc++/28457] New: " drow at gcc dot gnu dot org 2006-07-26 11:26 ` [Bug libstdc++/28457] " pcarlini at suse dot de 2006-07-26 13:11 ` drow at gcc dot gnu dot org 2006-07-26 13:27 ` pcarlini at suse dot de 2006-07-26 14:55 ` pcarlini at suse dot de 2006-08-25 17:19 ` pcarlini at suse dot de 2006-10-06 10:41 ` bkoz at gcc dot gnu dot org [this message] 2006-10-06 16:07 ` pcarlini at suse dot de 2009-07-15 7:38 ` steven at gcc dot gnu dot org [not found] <bug-28457-4@http.gcc.gnu.org/bugzilla/> 2011-05-21 2:27 ` bkoz at gcc dot gnu.org 2011-05-24 3:00 ` bkoz 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=20061006104106.14488.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: linkBe 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).