From: Christopher Quinn <cq@htec.demon.co.uk>
To: Markus Mottl <markus@oefai.at>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: [Caml-list] GC and preventing data relocation
Date: Fri, 21 Mar 2003 01:15:50 +0000 [thread overview]
Message-ID: <3E7A67C6.5030302@htec.demon.co.uk> (raw)
In-Reply-To: <20030321000134.GA17993@fichte.ai.univie.ac.at>
Markus Mottl wrote:
>>a) if you have C-heap struct specific to each invocation, register the
>>field holding the string pointer as a caml root, deregister it on
>>completion. but that is more overhead.
>
>
> I don't quite understand this solution. How should this prevent the
> string from being relocated if the string was allocated in the OCaml-heap?
it wouldn't, but at least the pointer to it is changed also. and the
assumption i made was that the glue code knows where it is keeping its
pointer to the string.
>
>
>>b) add a CString_tag to the set of value tags, modify the compactor()
>>routine to take acccount of it, and change the tag of a regular string
>>at runtime.
>>unfortunately this scheme greatly inconveniences the design of the
>>compactor and would likely slow it down.
>
>
> And wouldn't be particulary portable...
what 3rd party modification to the distributed caml runtime is!?
- chris
-------------------
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
next prev parent reply other threads:[~2003-03-21 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 15:16 Markus Mottl
2003-03-20 18:28 ` Christopher Quinn
2003-03-21 0:01 ` Markus Mottl
2003-03-21 1:15 ` Christopher Quinn [this message]
2003-03-21 12:03 ` Markus Mottl
2003-03-21 16:15 ` Damien Doligez
2003-03-21 16:35 ` Markus Mottl
2003-03-24 6:14 ` Nicolas Cannasse
2003-03-24 8:58 ` Markus Mottl
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=3E7A67C6.5030302@htec.demon.co.uk \
--to=cq@htec.demon.co.uk \
--cc=caml-list@inria.fr \
--cc=markus@oefai.at \
/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