public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Delesley Hutchins <delesley@google.com>
Cc: Diego Novillo <dnovillo@google.com>, gcc <gcc@gcc.gnu.org>,
	Ollie Wild <aaw@google.com>, 	Le-Chun Wu <lcwu@google.com>
Subject: Re: Announce - Thread safety annotations no longer supported in GCC
Date: Thu, 19 Apr 2012 16:25:00 -0000	[thread overview]
Message-ID: <CA+=Sn1n40QkjfTTx4S2GdHMSVYQg7uzQdGjR0Awg7MEBDxoDOA@mail.gmail.com> (raw)
In-Reply-To: <CAF6KqwVXHpV-WWr_GuDV1yHw-MbCVAhiJCCt6aR8NWnOS2xMYQ@mail.gmail.com>

On Thu, Apr 19, 2012 at 8:44 AM, Delesley Hutchins <delesley@google.com> wrote:
> 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,

No, that it does not help at all.  This seems like a high level issue
of the problem rather than describing the reasons why GIMPLE will
never work correctly for your usage.  Maybe we can expand it for your
usage but we need to better understand what it is lacking.

Thanks,
Andrew Pinski


>
>  -DeLesley
>
> On Thu, Apr 19, 2012 at 8:15 AM, Andrew Pinski <pinskia@gmail.com> wrote:
>> On Thu, Apr 19, 2012 at 7:15 AM, Diego Novillo <dnovillo@google.com> wrote:
>>>
>>> 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.  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.
>>
>> Thanks,
>> Andrew Pinski
>>
>>>
>>> I've updated the wiki page and moved the branch out of the active
>>> development branches in svn.html.
>>>
>>>
>>> Diego.
>
>
>
> --
> DeLesley Hutchins | Software Engineer | delesley@google.com | 505-206-0315

  reply	other threads:[~2012-04-19 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFOgFcSO9NRXprgW+LxkcOCjttzGZiqyugwbLPbrLpQUqMkmHA@mail.gmail.com>
2012-04-19 14:15 ` Diego Novillo
2012-04-19 15:15   ` Andrew Pinski
2012-04-19 15:44     ` Delesley Hutchins
2012-04-19 16:25       ` Andrew Pinski [this message]
2012-04-19 17:30         ` Delesley Hutchins
2012-04-19 19:15           ` Andrew Pinski
2012-04-19 20:20             ` Diego Novillo
2012-04-19 21:10               ` Delesley Hutchins
2012-04-20  8:50               ` Richard Guenther
2012-04-19 20:55             ` Delesley Hutchins
2012-04-20  2:31           ` Miles Bader
2012-04-20 17:55             ` Delesley Hutchins
2012-04-20 15:40 Manuel López-Ibáñez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+=Sn1n40QkjfTTx4S2GdHMSVYQg7uzQdGjR0Awg7MEBDxoDOA@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=aaw@google.com \
    --cc=delesley@google.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=lcwu@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).