From: Raoul Duke <raould@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] concurrent gc?
Date: Mon, 28 Jul 2014 10:34:02 -0700 [thread overview]
Message-ID: <CAJ7XQb4Q8FSEOrNB0-anYmMaSKZqw-8zOrLc64eRN2zck5vSKg@mail.gmail.com> (raw)
In-Reply-To: <20140728112431.GC26816@frosties>
>> There are also other tricks such as changing the tag of a block to avoid
>> scanning, but I wouldn't advise to use it unless you really know what you
>> are doing...
> That is actualy something that should be fixed in the compiler. There
> are some special cases that use special tags, e.g. a record only
> containing floats will be tagges as float array. But any record that
> contains no pointers should be tagged so it isn't needlessly scanned.
> Afaik that doesn't happen yet.
anybody who understands those words willing to open a bug report on it? ;-)
next prev parent reply other threads:[~2014-07-28 17:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 23:34 Raoul Duke
2014-07-24 0:05 ` John F. Carr
2014-07-24 0:08 ` Raoul Duke
2014-07-24 0:44 ` John F. Carr
2014-07-24 0:45 ` Raoul Duke
2014-07-24 15:24 ` Shayne Fletcher
2014-07-24 3:45 ` Malcolm Matalka
2014-07-24 5:58 ` Anthony Tavener
2014-07-28 11:20 ` Goswin von Brederlow
2014-07-24 6:58 ` Nicolas Boulay
2014-07-24 7:38 ` Malcolm Matalka
2014-07-24 15:36 ` Fabrice Le Fessant
2014-07-24 15:39 ` Malcolm Matalka
2014-07-24 16:44 ` Fabrice Le Fessant
2014-07-25 7:18 ` Nicolas Boulay
2014-07-28 11:26 ` Goswin von Brederlow
2014-07-28 11:24 ` Goswin von Brederlow
2014-07-28 17:34 ` Raoul Duke [this message]
2014-07-29 4:25 ` Gabriel Scherer
2014-07-29 4:49 ` ygrek
2014-07-29 10:01 ` Goswin von Brederlow
2014-07-29 10:29 ` ygrek
2014-07-31 11:10 ` Goswin von Brederlow
2014-07-29 17:23 ` Raoul Duke
2014-12-19 0:58 ` Jon Harrop
2014-07-31 14:26 ` Richard W.M. Jones
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=CAJ7XQb4Q8FSEOrNB0-anYmMaSKZqw-8zOrLc64eRN2zck5vSKg@mail.gmail.com \
--to=raould@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
/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