From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 8E18C7FA4D for ; Mon, 28 Jul 2014 13:24:34 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.17.12; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.17.12; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.17.12; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuoBAGUy1lPU4xEMnGdsb2JhbABZ0gqFaAGBFBYQAQEBAQEGDQkJFCmEBAEFOk8LGAklDwUoiGEBGLVNH4dJF49TFoMZgRsBBJtLhwcTkH4 X-IPAS-Result: AuoBAGUy1lPU4xEMnGdsb2JhbABZ0gqFaAGBFBYQAQEBAQEGDQkJFCmEBAEFOk8LGAklDwUoiGEBGLVNH4dJF49TFoMZgRsBBJtLhwcTkH4 X-IronPort-AV: E=Sophos;i="5.01,748,1400018400"; d="scan'208";a="73055356" Received: from mout.web.de ([212.227.17.12]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Jul 2014 13:24:34 +0200 Received: from frosties.localnet ([78.43.112.61]) by smtp.web.de (mrweb103) with ESMTPSA (Nemesis) id 0MXYWA-1WwtZW3v2k-00WV0N for ; Mon, 28 Jul 2014 13:24:33 +0200 Received: from mrvn by frosties.localnet with local (Exim 4.82) (envelope-from ) id 1XBj2d-0007RD-L0 for caml-list@inria.fr; Mon, 28 Jul 2014 13:24:31 +0200 Date: Mon, 28 Jul 2014 13:24:31 +0200 From: Goswin von Brederlow To: caml-list@inria.fr Message-ID: <20140728112431.GC26816@frosties> References: <21456.19915.45180.915211@gargle.gargle.HOWL> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Provags-ID: V03:K0:eKKafu3MvYaIwdfDb63UJxthyziVl/xL3oNujYkORPYDsIxoqs5 kwZDtsD1PeDngny3RJnFLI4VsZBBltTf9jSmTuJUZ4NG2xU/0bsMQLTjppJjT5Iv6i4S8g8 fLWOK8wF1lKVgXj7YPDuyqL+8B6X8YueiznGiTbl8ph5Mn7c8Zh0iddv7iLYs5a8Cb9oYxD HSXAP4DWaNDexPjh4v4eQ== Subject: Re: [Caml-list] concurrent gc? On Thu, Jul 24, 2014 at 06:44:21PM +0200, Fabrice Le Fessant wrote: > 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... > > --Fabrice 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. MfG Goswin