From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16405 invoked by alias); 17 Jun 2008 18:50:05 -0000 Received: (qmail 16394 invoked by uid 22791); 17 Jun 2008 18:50:04 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 17 Jun 2008 18:49:42 +0000 Received: from zps37.corp.google.com (zps37.corp.google.com [172.25.146.37]) by smtp-out.google.com with ESMTP id m5HInako002975 for ; Tue, 17 Jun 2008 19:49:36 +0100 Received: from an-out-0708.google.com (anab36.prod.google.com [10.100.53.36]) by zps37.corp.google.com with ESMTP id m5HInZFU021726 for ; Tue, 17 Jun 2008 11:49:35 -0700 Received: by an-out-0708.google.com with SMTP id b36so2412576ana.70 for ; Tue, 17 Jun 2008 11:49:35 -0700 (PDT) Received: by 10.100.154.19 with SMTP id b19mr766363ane.98.1213728575158; Tue, 17 Jun 2008 11:49:35 -0700 (PDT) Received: by 10.100.131.19 with HTTP; Tue, 17 Jun 2008 11:49:34 -0700 (PDT) Message-ID: <82091ad70806171149w48099ddal9d47c402ac134dcf@mail.gmail.com> Date: Tue, 17 Jun 2008 18:50:00 -0000 From: "Le-Chun Wu" To: tromey@redhat.com Subject: Re: Thread safety annotations and analysis in GCC Cc: gcc@gcc.gnu.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <82091ad70806091629q5a585d1fq4942d9c5ed3d6a69@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2008-06/txt/msg00376.txt.bz2 Tom, Thanks a lot for pointing us to the sparse annotations. We will take a look and see what its support looks like. Le-chun On Sun, Jun 15, 2008 at 2:43 PM, Tom Tromey wrote: >>>>>> "Le-Chun" == Le-Chun Wu writes: > > Le-Chun> Here is the design doc for the proposed annotations: > Le-Chun> http://docs.google.com/Doc?id=ddqtfwhb_0c49t6zgr > > I am curious to know how this compares to the kind of lock checking > implemented in sparse, and in particular whether sparse annotations > could easily be translated to this style. > > Tom >