From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27083 invoked by alias); 19 Apr 2012 15:44:29 -0000 Received: (qmail 26995 invoked by uid 22791); 19 Apr 2012 15:44:27 -0000 X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-yx0-f175.google.com (HELO mail-yx0-f175.google.com) (209.85.213.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 19 Apr 2012 15:44:14 +0000 Received: by yenm3 with SMTP id m3so4865285yen.20 for ; Thu, 19 Apr 2012 08:44:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=imzt2pd5v8ZH9CiuxcskobL7b0KtIRa4KMChlXpUhhg=; b=Dw9kwed0WyOcMDKjCIMqK/Ty+zqM6eMuY+eMX8Z4BhvGXqcePMGTsL0zJ6EoVxP2PO fD5xIAcUKI5Y8a6s/LvNv5V7+ZTosY8TKYHbcQv8K0q6lXGbZQHZNZwVx01eWJMTvSEJ PxQkJJpjuzTBvaVrXEctLzSo2bgdaFNSn1Y2e5L9pcznspFtySIQH48fC1IyrsyNC1AT pyQxiTy9DXhjvdoVdoA+x2FeewRfiLKm0se4hx8IhFSKRtSjpcyC8kQOJxXv6e8vmiUx Q0x4PAXaU4gwQUBGLlfz7acjBn1kZUsSXDJTEopcDuVDvTnrjkUUjND91RTRfm6alfZY lMnA== Received: by 10.60.7.200 with SMTP id l8mr394057oea.52.1334850253807; Thu, 19 Apr 2012 08:44:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.7.200 with SMTP id l8mr394047oea.52.1334850253703; Thu, 19 Apr 2012 08:44:13 -0700 (PDT) Received: by 10.182.245.17 with HTTP; Thu, 19 Apr 2012 08:44:13 -0700 (PDT) In-Reply-To: References: <4F901DEA.1060401@google.com> Date: Thu, 19 Apr 2012 15:44:00 -0000 Message-ID: Subject: Re: Announce - Thread safety annotations no longer supported in GCC From: Delesley Hutchins To: Andrew Pinski Cc: Diego Novillo , gcc , Ollie Wild , Le-Chun Wu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQkhmc8kfoPSetRS6zt97WB4iORyFKMnUCj52cAXX0lyFpS0H8yu+BMt65N7/T5yGlu/xB/98lXlUxOFOQmmf7op/Hl1iRrMlWsOzSk3wwJYPop1uA4mflfGdOJhtiNaaxkux7lV 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: 2012-04/txt/msg00717.txt.bz2 The gcc version has been difficult to support and maintain, due mainly to the fact that the GIMPLE intermediate language was never designed for static analysis. The abstract syntax tree provided by Clang is an easier data structure to work with for front-end analyses of this kind. Moreover, the gcc implementation of annotalysis has some issues that make an eventual merge into trunk somewhat unlikely, and annotalysis is of little use to people outside of google as long as it stays in google/main. The clang implementation has been in trunk from the beginning. Hope that explains it a bit better, -DeLesley On Thu, Apr 19, 2012 at 8:15 AM, Andrew Pinski wrote: > On Thu, Apr 19, 2012 at 7:15 AM, Diego Novillo wrot= e: >> >> We have decided to terminate the thread safety annotation project in >> GCC. >> >> The current implementation is in the branch google/main for those >> interested in using it. =A0We will not be pursuing a merge into trunk. >> Instead, we have started implementing the same functionality in Clang. > > What went into making this decision? =A0I know lot of folks will almost > never go over to using clang since it means supporting one extra > front-end. =A0I am thinking of the embedded folks here where they cannot > afford supporting something as new as clang for their customers. > > Thanks, > Andrew Pinski > >> >> I've updated the wiki page and moved the branch out of the active >> development branches in svn.html. >> >> >> Diego. --=20 DeLesley Hutchins | Software Engineer | delesley@google.com | 505-206-0315