From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Effect of Windows LLP64 architecture on 64 bit MingW OCaml
Date: Sat, 24 Oct 2015 10:54:41 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE333E3@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CAPFanBFWj+kArZn6Jo-RKH-8gKNk1kkKw6JEo+6rExo3xe4EZA@mail.gmail.com>
Dear Gabriel,
I think the information that dedicated 64 bit makefiles are available is important. We do things which require a lot of RAM, so 32 bit won't work. Also many people will think that 32 bit toolchains are outdated and it doesn't make a good impression if the docs mention a 32 bit windows build but not a 64 bit windows build. I will first test how well the 64 bit mingw stuff works and the request a change as you suggested.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2015-10-24 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 13:57 Soegtrop, Michael
2015-10-23 16:13 ` Xavier Leroy
2015-10-24 9:29 ` Soegtrop, Michael
2015-10-24 10:05 ` Adrien Nader
2015-10-24 10:09 ` Gabriel Scherer
2015-10-24 10:54 ` Soegtrop, Michael [this message]
2015-10-24 10:59 ` David Allsopp
2015-10-26 8:25 ` Soegtrop, Michael
2015-10-24 11:16 ` Gerd Stolpmann
2015-10-26 8:42 ` Soegtrop, Michael
2015-10-26 19:04 ` Adrien Nader
2015-10-24 10:49 Soegtrop, Michael
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=0F7D3B1B3C4B894D824F5B822E3E5A172CE333E3@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
/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