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++/40094] FAIL: ext/throw_allocator/deallocate_global.cc execution test
Date: Fri, 29 May 2009 01:20:00 -0000 [thread overview]
Message-ID: <20090529012031.13363.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40094-276@http.gcc.gnu.org/bugzilla/>
------- Comment #21 from bkoz at gcc dot gnu dot org 2009-05-29 01:20 -------
Yeah Paolo, didn't these this was due to your rework. I think the test cases
are ok now, seems like a better starting place although we may need to add
// { dg-require-cxa-atexit "" }
on more of these.
Actually had another idea about reworking throw_allocator, as attached for
trunk at some point. Although hackish, the current version's weird linkage gets
the job done without exports so don't see any need to mess with 4.4 branch.
My plan is to work through the testsuite failures first and then when that dust
settles down then merge in the reworked throw_allocator.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094
next prev parent reply other threads:[~2009-05-29 1:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 19:01 [Bug libstdc++/40094] New: " danglin at gcc dot gnu dot org
2009-05-10 20:17 ` [Bug libstdc++/40094] " paolo dot carlini at oracle dot com
2009-05-17 15:28 ` paolo dot carlini at oracle dot com
2009-05-17 23:20 ` dave at hiauly1 dot hia dot nrc dot ca
2009-05-21 0:49 ` danglin at gcc dot gnu dot org
2009-05-21 9:15 ` paolo dot carlini at oracle dot com
2009-05-22 0:54 ` danglin at gcc dot gnu dot org
2009-05-22 1:07 ` paolo dot carlini at oracle dot com
2009-05-22 1:15 ` paolo dot carlini at oracle dot com
2009-05-22 1:29 ` paolo dot carlini at oracle dot com
2009-05-22 1:29 ` paolo at gcc dot gnu dot org
2009-05-22 1:30 ` danglin at gcc dot gnu dot org
2009-05-22 1:33 ` paolo at gcc dot gnu dot org
2009-05-22 1:42 ` danglin at gcc dot gnu dot org
2009-05-28 18:53 ` bkoz at gcc dot gnu dot org
2009-05-28 18:53 ` bkoz at gcc dot gnu dot org
2009-05-28 19:59 ` paolo dot carlini at oracle dot com
2009-05-28 20:09 ` paolo dot carlini at oracle dot com
2009-05-28 20:16 ` dave at hiauly1 dot hia dot nrc dot ca
2009-05-28 22:26 ` paolo dot carlini at oracle dot com
2009-05-29 1:13 ` bkoz at gcc dot gnu dot org
2009-05-29 1:20 ` bkoz at gcc dot gnu dot org [this message]
2009-07-30 20:23 ` danglin at gcc dot gnu dot org
[not found] <bug-40094-4@http.gcc.gnu.org/bugzilla/>
2023-05-16 19:41 ` pinskia at gcc dot gnu.org
2023-05-16 20:38 ` redi at gcc dot gnu.org
2023-05-16 20:47 ` danglin at gcc dot gnu.org
2023-05-16 20:55 ` redi 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=20090529012031.13363.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).