From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19439 invoked by alias); 11 Feb 2004 04:40:41 -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 19429 invoked by uid 48); 11 Feb 2004 04:40:40 -0000 Date: Wed, 11 Feb 2004 04:40:00 -0000 Message-ID: <20040211044040.19428.qmail@sources.redhat.com> From: "ljrittle at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040106121715.13583.peturr02@ru.is> References: <20040106121715.13583.peturr02@ru.is> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/13583] [3.3/3.4/3.5 Regression] __use_cache not threadsafe X-Bugzilla-Reason: CC X-SW-Source: 2004-02/txt/msg01176.txt.bz2 List-Id: ------- Additional Comments From ljrittle at gcc dot gnu dot org 2004-02-11 04:40 ------- Without discounting this type of report (i.e. we want to fix this): On most/all supported CPU arches, we believe that this is a contained memory leak (bounded by number of threads competing to build the cache which itself is bound by number of threads) rather than failing to be threadsafe... As discussed on the list, we will not fix this for 3.3.X or 3.4. - Loren -- What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2004-01-06 18:48:12 |2004-02-11 04:40:40 date| | Target Milestone|3.4.0 |3.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13583