From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id PAA15998; Mon, 21 Oct 2002 15:46:41 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id PAA15757 for ; Mon, 21 Oct 2002 15:46:40 +0200 (MET DST) Received: from relay.rinet.ru (relay.rinet.ru [195.54.192.35]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g9LDkcD06971 for ; Mon, 21 Oct 2002 15:46:39 +0200 (MET DST) Received: (from uucp@localhost) by relay.rinet.ru (8.11.6/8.11.6) with UUCP id g9LDkcv20754 for caml-list@inria.fr; Mon, 21 Oct 2002 17:46:38 +0400 (MSD) X-Envelope-To: caml-list@inria.fr Received: from pc-9-4.stormoff (PC-9-4) [192.168.0.100] by stormoff with esmtp (Exim 3.12 #1 (Debian)) id 183csv-0004uH-00; Mon, 21 Oct 2002 17:46:21 +0400 X-Comment-To: Xavier Leroy To: caml-list@inria.fr Subject: Re: [Caml-list] ocamlopt / ocaml -custom and C compiler References: <3daf2a4f.865261093@smtp.interaccess.com> <87zntchwmc.dlv@wanadoo.fr> <20021021151819.D12164@pauillac.inria.fr> From: Dmitry Bely Date: Mon, 21 Oct 2002 17:46:24 +0400 In-Reply-To: <20021021151819.D12164@pauillac.inria.fr> (Xavier Leroy's message of "Mon, 21 Oct 2002 15:18:19 +0200") Message-ID: <3cqzlxan.fsf@mail.ru> User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Economic Science (Windows [1]), i586-pc-win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk Xavier Leroy writes: >> BTW, why Ocaml developers decided that ocamlopt should generate >> camlprim?.c in C, but not directly in Assembler? > > Unless I'm mistaken, ocamlopt doesn't generate a camlprim.c file; > ocamlc -custom does. The reason for going through C in this case is > that ocamlc has no knowledge of the assembly language for the > processor: ocamlc is designed to work for any system that provides an > ANSI C compiler. Sorry, my mistake. But ocamlopt uses C compiler for linking. Why not to use the link utility itself (say, link.exe for MSVC build)? >> This is especially inconvenient for >> Windows users where C compiler is not the part of OS distribution and >> should be bought separately... > > We have addressed this issue in at least two different ways. One is > the dynamic loading of C/Caml stub code, as implemented since release > 3.04. Now is the time for external C libraries to use this mechanism, > especially if they are to run under Windows. The second answer to > this problem is the Mingw port. Don't complain about lack of options :-) I am aware of MinGW port :-), but thank you for the detailed explanation. - Dmitry Bely ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners