Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 51188 invoked from network); 21 May 2007 23:17:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 23:17:12 -0000 Received: (qmail 38960 invoked by uid 500); 21 May 2007 23:17:18 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 38948 invoked by uid 500); 21 May 2007 23:17:18 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 38937 invoked by uid 99); 21 May 2007 23:17:18 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 16:17:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 16:17:10 -0700 Received: from qxvcexch01.ad.quovadx.com ([192.168.170.59]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l4LNGjnp018506 for ; Mon, 21 May 2007 23:16:45 GMT Received: from [10.70.3.113] ([10.70.3.113]) by qxvcexch01.ad.quovadx.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 21 May 2007 17:15:26 -0600 Message-ID: <46522879.6090409@roguewave.com> Date: Mon, 21 May 2007 17:17:13 -0600 From: Martin Sebor Organization: Rogue Wave Software User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: Intel Thread Checker Support References: <465118A9.30407@roguewave.com> <0B39DB22-C426-48B3-AAA2-560AF5F4FE70@roguewave.com> In-Reply-To: <0B39DB22-C426-48B3-AAA2-560AF5F4FE70@roguewave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 May 2007 23:15:26.0119 (UTC) FILETIME=[EA2CE370:01C79BFD] X-Virus-Checked: Checked by ClamAV on apache.org Liviu Nicoara wrote: > On May 20, 2007, at 11:57 PM, Martin Sebor wrote: > >> Eric Lemings wrote: >>> Questions for STDCXX users and maintainers regarding Intel Thread >>> Checker (ITC): >>> 1. Would STDCXX benefit from ITC support? >> >> I don't know :) Does it reveal any problems in our code? Is it worth >> the effort? From what I've heard from Liviu it sounds like a quite >> a bit of work for not a whole lot of benefit. > > The main benefit of this exercise is to eliminate the false positives in > the ITC analysis of the code which uses stdcxx. This is the exactly what > I have avoided in the other libraries in the Core package by using the > ITC synchronization API. That's a benefit to the users of stdcxx, not the project itself. Which isn't to say that such a benefit is not unimportant, of course. > >> I think it would be good to see examples of bug in our code revealed >> by the tool. > > I agree it would be a spectacular demonstration of the usefulness of the > tool but -- based on my knowledge of the stdcxx code -- I strongly doubt > I can demonstrate an MT bug in it. Do you know of an unresolved MT bug > in stdcxx? There is a problem in locale (as usual, sigh :( A couple of our thread safety tests have been crashing: 22_mt and 22_time_put_mt. Martin