|| ||Delesley Hutchins <delesley-AT-google.com> |
|| ||Andrew Pinski <pinskia-AT-gmail.com> |
|| ||Re: Announce - Thread safety annotations no longer supported in GCC |
|| ||Thu, 19 Apr 2012 08:44:13 -0700|
|| ||Diego Novillo <dnovillo-AT-google.com>, gcc <gcc-AT-gcc.gnu.org>, Ollie Wild <aaw-AT-google.com>, Le-Chun Wu <lcwu-AT-google.com>|
|| ||Article, Thread
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
Hope that explains it a bit better,
On Thu, Apr 19, 2012 at 8:15 AM, Andrew Pinski <email@example.com> wrote:
> On Thu, Apr 19, 2012 at 7:15 AM, Diego Novillo <firstname.lastname@example.org> wrote:
>> We have decided to terminate the thread safety annotation project in
>> The current implementation is in the branch google/main for those
>> interested in using it. We will not be pursuing a merge into trunk.
>> Instead, we have started implementing the same functionality in Clang.
> What went into making this decision? I know lot of folks will almost
> never go over to using clang since it means supporting one extra
> front-end. I am thinking of the embedded folks here where they cannot
> afford supporting something as new as clang for their customers.
> Andrew Pinski
>> I've updated the wiki page and moved the branch out of the active
>> development branches in svn.html.
DeLesley Hutchins | Software Engineer | email@example.com | 505-206-0315
to post comments)