From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13615 invoked by alias); 2 May 2005 13:30:35 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12792 invoked by alias); 2 May 2005 13:30:17 -0000 Date: Mon, 02 May 2005 13:30:00 -0000 Message-ID: <20050502133017.12790.qmail@sourceware.org> From: "jkanze at cheuvreux dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050502114518.21334.jkanze@cheuvreux.com> References: <20050502114518.21334.jkanze@cheuvreux.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string X-Bugzilla-Reason: CC X-SW-Source: 2005-05/txt/msg00257.txt.bz2 List-Id: ------- Additional Comments From jkanze at cheuvreux dot com 2005-05-02 13:30 ------- Subject: Re: Lack of Posix compliant thread safety in std::basic_string |> Two quick comments: 1- I'd like to keep open either 10350 or |> this one, I don't see much value in keeping open both. Ok? In that case, I'd go for this one. It mentions one of the places where g++ documentation suggests that this shouldn't work. And it mentions the Posix standard as an argument as to why it should. |> 2- I'm not aware of any real cure for this kind of problems |> within a RC implementation. Are you? pthread_mutex_lock:-). Of course, performance will take a serious hit. -- James Kanze mailto:james.kanze@free.fr Conseils en informatique orientée objet/ Beratung in objektorientierter Datenverarbeitung 9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34 "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Credit Agricole Cheuvreux except where provided for in a written agreement. Credit Agricole Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Credit Agricole Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein." -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334