From: "Doug Kwan (關振德)" <dougkwan@google.com>
To: "Jason Merrill" <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: ping [PATCH] Fix a deadlock bug in static variable initialization in libsupc++
Date: Thu, 16 Aug 2007 05:38:00 -0000 [thread overview]
Message-ID: <498552560708152237o76075b60idbbf3f3a8e4e5212@mail.gmail.com> (raw)
In-Reply-To: <46C37623.1010308@redhat.com>
Hi Jason,
That's reasonable. I can change that. Actually, we have don't need
the skip list for system with 32-bit pthread ID. Is it desirable to
support low-overhead recursive init detection in those systems?
-Doug
2007/8/15, Jason Merrill <jason@redhat.com>:
> Thanks for fixing this, and sorry about the delay.
>
> It seems like the skip list code is only used to support throwing the
> recursive_init_exception. I think I'd prefer to just drop that and let
> recursive initialization deadlock (which is allowed under undefined
> behavior) rather than add that overhead to the common case.
>
> Jason
>
next prev parent reply other threads:[~2007-08-16 5:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 20:56 Doug Kwan (關振德)
2007-08-15 21:54 ` Jason Merrill
2007-08-16 5:38 ` Doug Kwan (關振德) [this message]
2007-08-16 18:55 ` Jason Merrill
2007-09-17 23:30 ` Doug Kwan (關振德)
2007-09-18 7:19 ` Eric Botcazou
2007-09-18 8:43 ` Doug Kwan (關振德)
2007-09-20 20:01 ` Jason Merrill
2007-10-03 21:56 ` Doug Kwan (關振德)
2007-10-03 22:08 ` Benjamin Kosnik
2007-10-03 22:24 ` Paolo Carlini
2007-10-04 0:20 ` Doug Kwan (關振德)
2007-10-05 5:41 ` Jason Merrill
[not found] ` <m3y7f49goe.fsf@fleche.redhat.com>
2007-09-18 22:52 ` Doug Kwan (關振德)
2007-10-05 21:18 ` Build error with " Hans-Peter Nilsson
2007-10-05 21:44 ` Jason Merrill
2007-10-05 22:21 ` Hans-Peter Nilsson
2007-10-07 17:51 ` Doug Kwan (關振德)
2007-10-07 19:32 ` Hans-Peter Nilsson
2007-10-07 20:41 ` Andrew Pinski
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=498552560708152237o76075b60idbbf3f3a8e4e5212@mail.gmail.com \
--to=dougkwan@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@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).