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++/22309] mt allocator doesn't pthread_key_delete it's keys Date: Fri, 09 Sep 2005 09:19:00 -0000 [thread overview] Message-ID: <20050909091947.26962.qmail@sourceware.org> (raw) In-Reply-To: <20050705135434.22309.jakub@redhat.com> ------- Additional Comments From bkoz at gcc dot gnu dot org 2005-09-09 09:19 ------- Hey Jakub. Yeah, I think this can be back-ported. I put in my patch, which looks pretty good on x86/linux. We could proably do something more elaborate to not duplicate some of the symbols but I'm feeling lazy... this is good enough. Sorry about the confusion about the static freelist_mutex. Yes, this was what I was getting at by "linkage clarity" ... I think we are on the same page. Yes, this is a good idea, and I'll clean this up too as a follow-on patch. Umm... so, no, I don't get what you are getting at WRT destructors in libstdc++.so. I think you mean functions in testsuite_shared.so that are asm destrutors but that use __mt_alloc to do allocations or something. You mean, what then? Maybe we'd both be better off if you came up with an example... I think just static ordering in this file will work. Won't that just work? Man, I want that to work. If not, then the init priorty stuff can be re-added. The thing is, there are no config tests for init priority... ..... I thought support of that was kind of dodgy, non-ELF... if this feature is going to be used, there are other things with __ioinit that can also be done. Anyway. Of more immediate concern is that the testsuite dejagnu hacking is quite weak. For instance, The testsuite file should just be run on linux, so I think that is ok. But the shared object is unconditionally compiled, even for --disable-shared builds.... also, compiled with a complete hack for flags, likely to only work on linux... It is kind of funny, just to be re-creating an autoconf way of doing this, but doing it in dejagnu. Ugh. Some of this stuff would be easier if we could use Make to build instead of dejagnu.... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22309
next prev parent reply other threads:[~2005-09-09 9:19 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-05 13:54 [Bug libstdc++/22309] New: " jakub at redhat dot com 2005-07-05 16:27 ` [Bug libstdc++/22309] " pcarlini at suse dot de 2005-07-05 16:32 ` pcarlini at suse dot de 2005-07-05 16:48 ` jakub at redhat dot com 2005-07-05 16:55 ` pcarlini at suse dot de 2005-07-14 12:48 ` jakub at redhat dot com 2005-07-14 13:01 ` jakub at redhat dot com 2005-07-14 13:38 ` jakub at redhat dot com 2005-07-14 17:06 ` pinskia at gcc dot gnu dot org 2005-08-26 18:01 ` bkoz at gcc dot gnu dot org 2005-09-01 21:02 ` bkoz at gcc dot gnu dot org 2005-09-09 8:26 ` jakub at gcc dot gnu dot org 2005-09-09 9:19 ` bkoz at gcc dot gnu dot org [this message] 2005-09-09 18:21 ` bkoz at gcc dot gnu dot org 2005-09-12 4:49 ` cvs-commit at gcc dot gnu dot org 2005-09-12 19:03 ` bkoz at gcc dot gnu dot org 2005-09-13 19:40 ` bkoz at gcc dot gnu dot org 2005-09-20 5:25 ` [Bug libstdc++/22309] mt allocator doesn't pthread_key_delete its keys cvs-commit at gcc dot gnu dot org 2005-09-24 14:45 ` Woebbeking at web dot de 2005-09-26 23:03 ` bkoz at gcc dot gnu dot org 2005-09-27 14:38 ` Woebbeking at web dot de 2005-09-27 14:43 ` jakub at gcc dot gnu dot org 2005-09-28 17:16 ` Woebbeking at web dot de
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=20050909091947.26962.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).