This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: AMD64: dead-lock issue with gcc-4_0-branch libstdc++ and POSIX write locks.

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: Karel Gardas <kgardas at objectsecurity dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>
Cc: gcc at gcc dot gnu dot org
Date: Sat, 14 May 2005 12:48:30 -0400
Subject: Re: AMD64: dead-lock issue with gcc-4_0-branch libstdc++ and POSIX write locks.
References: <Pine.LNX.4.63.0505141215010.4282@silence.gardas.net> <Pine.LNX.4.63.0505141835050.5537@silence.gardas.net>

On May 14, 2005, at 12:41 PM, Karel Gardas wrote:

Hello,

just short follow-up to this thread. I've also tried gcc head (from today) and its libstdc++ is OK, i.e. no dead-lock presented. I've also verified that it is libstdc++ and not libgcc_s.

Any idea what's going wrong with GCC 4.0.x's libstdc++?

I have no idea but it might be better if you had written to the libstdc++'s mailing list which the libstdc++ developers read. I already forwarded your original email there.

-- Pinski

References:
- AMD64: dead-lock issue with gcc-4_0-branch libstdc++ and POSIX writelocks.
  - From: Karel Gardas
- Re: AMD64: dead-lock issue with gcc-4_0-branch libstdc++ and POSIXwrite locks.
  - From: Karel Gardas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]