From: Christopher Li <sparse@chrisli.org>
To: Alberto Bertogli <albertito@blitiri.com.ar>
Cc: linux-sparse@vger.kernel.org, josh@kernel.org
Subject: Re: [PATCH] Support the __thread storage class
Date: Tue, 19 May 2009 03:00:40 -0700 [thread overview]
Message-ID: <70318cbf0905190300o1b82f2aax433b08248ac08c3a@mail.gmail.com> (raw)
In-Reply-To: <1242488218-19811-1-git-send-email-albertito@blitiri.com.ar>
On Sat, May 16, 2009 at 8:36 AM, Alberto Bertogli
<albertito@blitiri.com.ar> wrote:
> GCC supports a __thread storage class, used to indicate thread-local
> storage. It may be used alone, or with extern or static.
>
Thanks, I applied it to my tree already.
Chris
next prev parent reply other threads:[~2009-05-19 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70318cbf0904270020v78c98b7awee9ef64a6d60e14b@mail.gmail.com>
2009-05-16 15:36 ` [PATCH] Support the __thread storage class Alberto Bertogli
2009-05-19 10:00 ` Christopher Li [this message]
2009-04-27 0:44 Alberto Bertogli
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=70318cbf0905190300o1b82f2aax433b08248ac08c3a@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=albertito@blitiri.com.ar \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
/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 NNTP newsgroup(s).