public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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 its keys Date: Tue, 20 Sep 2005 05:25:00 -0000 [thread overview] Message-ID: <20050920052504.2442.qmail@sourceware.org> (raw) In-Reply-To: <20050705135434.22309.jakub@redhat.com> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-20 05:25 ------- Subject: Bug 22309 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-4_0-branch Changes by: bkoz@gcc.gnu.org 2005-09-20 05:24:50 Modified files: libstdc++-v3 : ChangeLog libstdc++-v3/config: linker-map.gnu libstdc++-v3/include/ext: mt_allocator.h libstdc++-v3/src: debug.cc locale_init.cc mt_allocator.cc pool_allocator.cc Log message: 2005-09-19 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/19265 PR libstdc++/22309 * include/ext/mt_allocator.h (__gnu_cxx::__create_handler): Remove. (__pool<true>::_M_destroy_thread_key): Compatibility only. (__pool<true>::_M_initialize(__destroy): Same. (__pool<true>::_M_initialize): New. (__pool<true>::_M_initialize_once): Nothing fancy. (__pool<true>::_M_once): Remove. (__common_pool): New. (__common_pool_base): New. (__per_type_pool): New. (__per_type_pool_base): New. * src/mt_allocator.cc: Same. * config/linker-map.gnu (__pool<true>::_M_initialize()): Add. 2005-09-19 Jakub Jelinek <jakub@redhat.com> PR libstdc++/19265 PR libstdc++/22309 * src/mt_allocator.cc (__gnu_internal::freelist_mutex): Make static. (__gnu_internal::__freelist): New type. (__gnu_internal::freelist): New variable. (__gnu_internal::_M_destroy_thread_key): New function. (__gnu_cxx::__pool<true>::_M_destroy): Don't delete _M_thread_freelist_initial. (__gnu_cxx::__pool<true>::_M_initialize): Make argument nameless. Don't use _M_thread_freelist and _M_thread_freelist_initial __pool<true> fields, instead use __gnu_internal::freelist fields, call gthread_key_create just once. Use __gnu_internal::_M_destroy_thread_key as key destructor. (__gnu_cxx::__pool<true>::_M_get_thread_id): Store size_t id rather than _Thread_record* in the thread specific value. Don't use _M_thread_freelist __pool<true> field, instead use __gnu_internal::freelist fields. (__gnu_cxx::__pool<true>::_M_destroy_thread_key): Do nothing. 2005-09-19 Benjamin Kosnik <bkoz@redhat.com> Jakub Jelinek <jakub@redhat.com> * src/debug.cc (iterator_base_mutex): Make static for internal linkage. * src/locale_init.cc (locale_mutex): Same. * src/mt_allocator.cc (freelist_mutex): Same. * src/pool_allocator.cc (palloc_init_mutex): Same. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.2917.2.83&r2=1.2917.2.84 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/config/linker-map.gnu.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.78.2.3&r2=1.78.2.4 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/include/ext/mt_allocator.h.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.45.8.1&r2=1.45.8.2 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/src/debug.cc.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.10&r2=1.10.18.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/src/locale_init.cc.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.15&r2=1.15.36.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/src/mt_allocator.cc.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.8&r2=1.8.22.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/src/pool_allocator.cc.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.2&r2=1.2.24.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22309
next prev parent reply other threads:[~2005-09-20 5:25 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-05 13:54 [Bug libstdc++/22309] New: mt allocator doesn't pthread_key_delete it's keys 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 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 ` cvs-commit at gcc dot gnu dot org [this message] 2005-09-24 14:45 ` [Bug libstdc++/22309] mt allocator doesn't pthread_key_delete its keys 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 [not found] <bug-22309-138@http.gcc.gnu.org/bugzilla/> 2006-03-03 17:55 ` bkoz at gcc dot gnu dot 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=20050920052504.2442.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).