public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Richard Henderson <rth@redhat.com>,
	gcc-patches@gcc.gnu.org, Eric Christopher <echristo@redhat.com>
Subject: Re: [basic-improvements] Remove __gthread_key_dtor
Date: Thu, 31 Oct 2002 13:20:00 -0000	[thread overview]
Message-ID: <20021031212027.GH5766@codesourcery.com> (raw)
In-Reply-To: <20021031210229.GA5029@redhat.com>

On Thu, Oct 31, 2002 at 01:02:29PM -0800, Richard Henderson wrote:
> 
> The tx5900 is one of the mips parts that doesn't have ll/sc,
> or indeed any atomic operations at all, so you have to have
> help from the OS.
> 
> Sony has a library through which you can create, lock and 
> unlock mutex objects.  If you don't destroy one of these,
> you leak it.
> 
> Eric has more details if you need them.

Okay, but what I don't get is why this translates to a requirement
that every registered TSD destructor hook call back into gthr.h.
In fact, I don't see what TSD has to do with mutexes at all.

zw

  reply	other threads:[~2002-10-31 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 14:33 Zack Weinberg
2002-10-29 23:50 ` Mark Mitchell
2002-10-31 11:18 ` Richard Henderson
2002-10-31 11:42   ` Zack Weinberg
2002-10-31 13:02     ` Richard Henderson
2002-10-31 13:20       ` Zack Weinberg [this message]
2002-10-31 13:57         ` Eric Christopher
2002-10-31 16:12           ` Zack Weinberg
2002-11-04 12:11             ` Eric Christopher
2002-11-04 17:08               ` Zack Weinberg
2002-11-04 18:19                 ` Eric Christopher
2002-10-31 12:04   ` Jason R Thorpe
2002-10-31 13:59     ` Eric Christopher

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=20021031212027.GH5766@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=echristo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.com \
    /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).