public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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 08:26:00 -0000	[thread overview]
Message-ID: <20050909082620.5025.qmail@sourceware.org> (raw)
In-Reply-To: <20050705135434.22309.jakub@redhat.com>


------- Additional Comments From jakub at gcc dot gnu dot org  2005-09-09 08:26 -------
Without init_priority, how can you be sure that other libstdc++.so destructors
will not be run after __gnu_internal::freelist is destructed?
If there are some destructors and they use the mt allocator (whether to allocate
some temporary memory or more likely to free some memory), won't it cause
big problems?

As for the lock being static, mt-allocator.cc is the only user of that lock,
so I don't see why it should be externally visible, even if just in libstdc++.a
(in libstdc++.so symbol versioning will hide it).  If there are other locks
used solely in one .cc file, I think they should be made static too.

Thanks for writing the testcase.  Haven't tried to compile your latest patch
yet, do the <ext/mt_allocator.h> changes preserve ABI compatibility?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22309


  parent reply	other threads:[~2005-09-09  8:26 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 [this message]
2005-09-09  9:19 ` bkoz at gcc dot gnu dot org
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=20050909082620.5025.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).