fa.caml Google Group

Re: [Caml-list] Unboxed float tuples

2009-11-08T21:25:58Z

On Sun, Nov 8, 2009 at 9:58 PM, Christophe Raffalli
I've been using {| |} -- a mesh of [| |] and { }
Cheers
______________________________ _________________
Caml-list mailing list. Subscription management:
[link]
Archives: [link]
Beginner's list: [link]

Re: [Caml-list] Unboxed float tuples

2009-11-08T20:59:13Z

I use (^ ^) and {^ ^} as bracket for my bindlib library.
The only defect is that you have to add spaces :
^)^))) should be written ^) ^) ))
You can look at the code of bindlib for more info ...
Cheers,
Christophe

Re: [Caml-list] Unboxed float tuples

2009-11-08T20:35:12Z

If you're willing to endure a whole program optimization pass then you can
avoid having to touch the GC and run-time by monomorphizing the code, e.g.
converting all tuples into monomorphic record types.

Re: [Caml-list] Unboxed float tuples

2009-11-08T20:10:05Z

I guess others have pointed out why this isn't so easy.
How about a syntax extension instead to turn a vector (| a, b, c |)
into { v0 = a; v1 = b; v2 = c }, and a standard type to solve the
module communication problem? I'm not sure if camlp4 will let you
define bracket lexemes like that.
Rich.

Re: [Caml-list] Unboxed float tuples

2009-11-08T19:39:25Z

Because tuples are generic data types. Access to records and arrays are
special cased- in the record case, because the compiler knows the type of
the record, in the array case because array access is via C code which
handles the special case. But the compiler needs to be able to compile
code with generic tuple accesses, like:

[Caml-list] Camlight version 0.80

2009-11-08T19:01:35Z

Bonjour,
Depuis quelque temps je maintiens des paquets camllight pour debian et ubuntu.
Ces paquets se trouvent sur
deb [link] lenny divers
(lenny peut être remplacé par woody, sarge (version 0.75) ou etch)
deb [link] karmic divers
karmic peut être remplacé par breezy, dapper edgy, feisty, gutsy, hardy,

Re: [Caml-list] OC4MC : OCaml for Multicore architectures

2009-11-08T18:11:50Z

The new SmartPumpkin release of OC4MC does a lot better. Specifically, the
version compiled with partial collections is now only 3.9x slower on a serial
ray tracer with n=9 (compared to 10x slower before). I'll try it in more
detail...

Re: [Caml-list] Unboxed float tuples

2009-11-08T17:29:52Z

Because polymorphic functions like fst would break (or would require extra
runtime checking).
Note that ('a * 'b) is pretty much the same as:
type ('a, 'b) tuple = { a : 'a; b : 'b }
- : int = 0
- : int = 0
whereas:
- : int = 254
Martin

~ TEEN TEASE ~

2009-11-08T16:54:31Z

.
~~~^^^~~~
============================== ====================
============================== ====================
ENTER HERE:
>>> [link] <<<
============================== ====================

Re: [Caml-list] Unboxed float tuples

2009-11-08T16:45:19Z

If you want to handle structs and vectors then you probably want structs
(value types) and not boxed representations like tuples and records anyway.

[Caml-list] Unboxed float tuples

2009-11-08T16:02:00Z

Tuples and records are represented the same way. However when it comes
to records with only floats fields we get a special unboxed
representation.
Why don't we get that for tuples of floats only ?
Using tuples (vs records) to handles points and vectors is
syntactically more lightweight (IMHO). More important it makes it

~ PANDA PICTURES ~

2009-11-08T15:36:42Z

.
~~~^^^~~~
============================== ====================
============================== ====================
ENTER HERE:
>>> [link] <<<
============================== ====================

~ BABY FABRIC ~

2009-11-08T13:07:42Z

.
~~~^^^~~~
============================== ====================
============================== ====================
ENTER HERE:
>>> [link] <<<
============================== ====================

Re: [Caml-list] Re: ATS versus Ocaml

2009-11-07T18:59:38Z

On x86, I get:
ATS: 0.189s
HLVM: 0.486s
OCaml: 0.552s
On x64, I get:
OCaml: 0.299s

Re: [Caml-list] compiling C library wrapper

2009-11-07T16:34:42Z

Thanks, I will look into that if I want to distribute wrapper code for
others to use. My current problems just involve using wrapper code
from other people with incomplete/broken Makefiles.
- Aaron
______________________________ _________________
Caml-list mailing list. Subscription management:
[link]

fa.caml Google Group

Re: [Caml-list] Unboxed float tuples

Re: [Caml-list] Unboxed float tuples

Re: [Caml-list] Unboxed float tuples

Re: [Caml-list] Unboxed float tuples

Re: [Caml-list] Unboxed float tuples

[Caml-list] Camlight version 0.80

Re: [Caml-list] OC4MC : OCaml for Multicore architectures

Re: [Caml-list] Unboxed float tuples

~~~~~~~~~~~~~~~ TEEN TEASE ~~~~~~~~~~~~~~~

Re: [Caml-list] Unboxed float tuples

[Caml-list] Unboxed float tuples

~~~~~~~~~~~~~~~ PANDA PICTURES ~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~ BABY FABRIC ~~~~~~~~~~~~~~~

Re: [Caml-list] Re: ATS versus Ocaml

Re: [Caml-list] compiling C library wrapper

~ TEEN TEASE ~

~ PANDA PICTURES ~

~ BABY FABRIC ~