And trampolines to eliminate tail calls that cannot be eliminated using goto.
However, trampolines are ~10x slower than TCO in the code gen.
With some care, gcc's sibcall mechanism can be exploited. For example,
by having one standard signature for all generated C functions, and
taking care not
The Weak module is never the right tool for implementing a cache.
I'm not disputing this, but I would like you hear your thoughts on
this topic. Why?
Weak references go away at the whim of the GC, not when it would be
useful to flush the cache. A longer explanation and more about weak
It's all very confusing to me because I thought Apple's assembler
*was* gas.
Sort of - if I understand it correctly, it is set of separately
maintained patches (for Mach-O) to an old version of gas. It is most
conveniently thought of as a different assembler. Not that it matters,
as the syntax
Suppose I want to build a server that runs on top of ocamlnet and
handles 10k+ connections.
ocamlnet seems to use select exclusively.
Any suggestions on how to add kernel poll? Is this possible even?
There is an ocaml wrapper for libevent: http://www.xs4all.nl/~mmzeeman/ocaml/
With that many
[...] There are good reasons to think that the
illusion of shared memory cannot be maintained in the presence of
hundreds of computing elements, even using cc-NUMA techniques
(i.e. hardware emulation of shared memory on top of high-speed
point-to-point links).
I'm not arguing any of your points
