From: Florian Weimer <fw@deneb.enyo.de>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Thread Local Storage
Date: Wed, 01 Mar 2006 08:37:55 +0100 [thread overview]
Message-ID: <87y7zuhay4.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1139955690.8591.799.camel@rosella.wigram> (skaller@users.sourceforge.net's message of "Wed, 15 Feb 2006 09:21:29 +1100")
> On Tue, 2006-02-14 at 22:40 +0100, Florian Weimer wrote:
>> > TLS is entirely a legacy application backwards compatibility hack
>> > designed to support badly designed C applications.
>>
>> TLS helps a lot on a certain register-starved architecture because you
>> don't need to keep a pointer to the thread data structure around in
>> case you don't need it (but called functions might).
>
> What's wrong with placing it on the stack?
Do you suggest to add an implicit argument to all function calls?
Unless you can optimize it away if it's not needed, the TLS approach
should still be faster for typical code.
prev parent reply other threads:[~2006-03-01 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 4:29 [Caml-list] " Jonathan Roewen
2006-02-13 10:05 ` Vincenzo Ciancia
2006-02-14 2:40 ` [Caml-list] " Jonathan Roewen
2006-02-14 4:06 ` skaller
2006-02-14 21:40 ` Florian Weimer
2006-02-14 22:21 ` skaller
2006-03-01 7:37 ` Florian Weimer [this message]
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=87y7zuhay4.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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).