Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Mathias Kende <mathias.kende@ens.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Difference between ocamlc and ocamlopt when marshalling reference
Date: Wed, 02 Jun 2010 18:40:29 +0200	[thread overview]
Message-ID: <4C06897D.3010008@inria.fr> (raw)
In-Reply-To: <1275480999.5099.19.camel@bohrium.pps.jussieu.fr>

Hi,

  The main difference is that "p" is a closure in bytecode, but just a
pointer in native code: in bytecode, "p" references "r", and so a
closure is needed; in native code, the reference to "r" in "p" is a
direct access to the module structure, and so "p" does not need to keep
a reference to "r". So, when you marshal "p" in bytecode, you follow the
closure and the reference, that are stored in "s", and they are
duplicated when "s" is unmarshalled.

  I think Marshal.Closures is only expected for hacking anyway, so you
should not really assume anything on its behavior ;-)

--Fabrice

Mathias Kende wrote, On 06/02/2010 02:16 PM:
> Hi,
> 
> I found a difference on the way global references used inside a function
> are handled with respect to marshalling between ocamlc and ocamlopt.
> 
> See the exemple below :
> 
> -------------- a.ml ---------------
> let r = ref 0
> let p () = Printf.printf "%d\n" !r
> let s = Marshal.to_string p [Marshal.Closures]
> let () = r := 1
> let q : unit -> unit = Marshal.from_string s 0
> let () = q ()
> -----------------------------------
> $ ocamlc a.ml
> $ ./a.out
> 0
> $ ocamlopt a.ml
> $ ./a.out 
> 1
> -----------------------------------
> 
> I am not sure which semantic is the "good" one. They are both
> interesting, but having only one is definitely simpler.
> 
> Is this a known problem ? is there fundamental reasons in the compilers
> for which it can not be changed ?
> 
> Cheers,
> 
> Mathias
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
> 

-- 
Fabrice LE FESSANT
Chercheur, Equipe ASAP
(As Scalable As Possible)
http://www.lefessant.net/

INRIA-Futurs, Bat P - 112
Parc Orsay Université
2-4, rue Jacques Monod
F-91893 Orsay Cedex, FRANCE


      reply	other threads:[~2010-06-02 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 12:16 Mathias Kende
2010-06-02 16:40 ` Fabrice Le Fessant [this message]

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=4C06897D.3010008@inria.fr \
    --to=fabrice.le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=mathias.kende@ens.fr \
    /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