This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [basic-improvements] Remove __gthread_key_dtor
- From: Eric Christopher <echristo at redhat dot com>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Richard Henderson <rth at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: 04 Nov 2002 18:40:55 -0800
- Subject: Re: [basic-improvements] Remove __gthread_key_dtor
- References: <20021029223346.GB31573@codesourcery.com><20021031191828.GU4764@redhat.com> <20021031194229.GB5766@codesourcery.com><20021031210229.GA5029@redhat.com> <20021031212027.GH5766@codesourcery.com><1036103481.1438.70.camel@ghostwheel><20021101001223.GK5766@codesourcery.com><1036442469.1509.22.camel@ghostwheel> <20021105010819.GC8919@egil.codesourcery.com>
> > Hrm. I was noticing that other ports use this method and that's why I
> > did - I also didn't see a way for it to work otherwise since there's no
> > general .c mechanism for it.
>
Right. Wasn't thinking clearly. :)
> If the underlying API doesn't support this, you're out of luck. But
> if there _is_ a way to get a callback run at thread exit time, you can
> just set one up in your init-once routine.
>
> Take a look at gthr-vxworks.h, config/vxlib.c, and config/t-vxworks on
> the gcc-3_4-basic-improvements-branch (after I commit them, which will
> happen in the next twenty minutes or so) -- they should give you some
> ideas.
>
Cool. Will do.
Thanks.
-eric
--
Yeah, I used to play basketball...