public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Le-Chun Wu" <lcwu@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Thread safety annotations and analysis in GCC
Date: Sun, 15 Jun 2008 21:44:00 -0000	[thread overview]
Message-ID: <m37icqnzlb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <82091ad70806091629q5a585d1fq4942d9c5ed3d6a69@mail.gmail.com> (Le-Chun Wu's message of "Mon\, 9 Jun 2008 16\:29\:47 -0700")

>>>>> "Le-Chun" == Le-Chun Wu <lcwu@google.com> 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

  parent reply	other threads:[~2008-06-15 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 23:30 Le-Chun Wu
2008-06-10  3:34 ` Andi Kleen
2008-06-10 18:30   ` Le-Chun Wu
2008-06-15 21:44 ` Tom Tromey [this message]
2008-06-17 18:50   ` Le-Chun Wu
2008-07-23  9:00 ` Ken Raeburn
2008-07-30  0:45   ` Le-Chun Wu

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=m37icqnzlb.fsf@fleche.redhat.com \
    --to=tromey@redhat.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).