This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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 POSIXwrite locks. (fwd)

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Karel Gardas <kgardas at objectsecurity dot com>
Cc: libstdc++ at gcc dot gnu dot org
Date: Mon, 16 May 2005 09:46:30 -0500
Subject: Re: AMD64: dead-lock issue with gcc-4_0-branch libstdc++ and POSIXwrite locks. (fwd)
References: <Pine.LNX.4.63.0505141857380.5537@silence.gardas.net><Pine.LNX.4.63.0505142017250.5537@silence.gardas.net>

> yet another short followup. When I tried to compile 4_0 branch sources, 
> exactly those which failed, with -enable-libstdcxx-allocator=mt, the 
> dead-lock has gone.

I haven't seen this before.

You'll need to provide a test case. There's no difference between
libstdc++ atomic ops between 3.4 and 4.0 on your architecture (although
unpatched 3.4.x does not support thread safe static locals, and 4.0.x
does). I can't think of anything different between head and 4.0 that
might impact this.

-benjamin

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

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