From: Goswin von Brederlow <goswin-v-b@web.de>
To: John Carr <jfc@MIT.EDU>
Cc: Benedikt Meurer <benedikt.meurer@googlemail.com>,
caml-list@yquem.inria.fr
Subject: Re: Value types
Date: Tue, 14 Dec 2010 10:43:39 +0100 [thread overview]
Message-ID: <87lj3sbsfo.fsf@frosties.localnet> (raw)
In-Reply-To: <201012121920.oBCJKdlV002949@department-of-alchemy.mit.edu> (John Carr's message of "Sun, 12 Dec 2010 14:20:39 -0500")
John Carr <jfc@MIT.EDU> writes:
>> I don't see the point of optimizing for x86-32
>
> I'm using 32 bit ocaml because my program uses too much memory in 64
> bit mode. If there were an ocaml that used 32 bit words in 64 bit
> mode, I would use that instead.
>
> Early 32 to 64 bit transitions offered 32 bit pointers with 64 bit
> registers, called TSO on Alpha and n32 on MIPS. AMD and Intel did not.
There is a patch for gcc for this for amd64.
It could be nice to implement this for ocaml too. It would mostly
improve the Int64 module. But the extra registers in 64bit mode should
help performance overall too.
MfG
Goswin
next prev parent reply other threads:[~2010-12-14 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 14:54 Value types (Was: [Caml-list] ocamlopt LLVM support) Jon Harrop
2010-12-12 15:55 ` Török Edwin
2010-12-12 17:14 ` Jon Harrop
2010-12-12 17:26 ` Török Edwin
2010-12-12 18:01 ` Jon Harrop
2010-12-12 18:22 ` Török Edwin
2010-12-12 19:09 ` Benedikt Meurer
2010-12-12 19:20 ` John Carr
2010-12-14 9:43 ` Goswin von Brederlow [this message]
2010-12-12 19:55 ` Török Edwin
2010-12-12 22:05 ` Jon Harrop
2010-12-12 22:27 ` Török Edwin
2010-12-12 23:41 ` Jon Harrop
2010-12-13 2:13 ` Eray Ozkural
2010-12-12 21:50 ` Jon Harrop
2010-12-13 8:43 ` Alain Frisch
2010-12-15 10:29 ` Benedikt Meurer
2010-12-15 13:15 ` Jon Harrop
2010-12-14 9:54 ` Value types Goswin von Brederlow
2010-12-12 19:53 ` Value types (Was: [Caml-list] ocamlopt LLVM support) Brian Hurt
2010-12-12 20:39 ` Jon Harrop
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=87lj3sbsfo.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=benedikt.meurer@googlemail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jfc@MIT.EDU \
/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