From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 50477BDDB for ; Sat, 27 Aug 2005 13:16:50 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j7RBGnHV009633 for ; Sat, 27 Aug 2005 13:16:49 +0200 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 NAA06669 for ; Sat, 27 Aug 2005 13:16:49 +0200 (MET DST) Received: from triton.rz.uni-saarland.de (triton.rz.uni-saarland.de [134.96.7.25]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j7RBGmdw009629 for ; Sat, 27 Aug 2005 13:16:49 +0200 Received: from uni-sb.de (uni-sb.de [134.96.7.230]) by triton.rz.uni-saarland.de (8.12.10/8.12.10) with ESMTP id j7RBGlew1532517 for ; Sat, 27 Aug 2005 13:16:47 +0200 (CEST) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.13.4/2005060800) with ESMTP id j7RBGiTn020796; Sat, 27 Aug 2005 13:16:44 +0200 (CEST) Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by cs.uni-sb.de (8.13.4/2005033000) with ESMTP id j7RBGhA6003873; Sat, 27 Aug 2005 13:16:43 +0200 (CEST) Received: from mail.st.cs.uni-sb.de (goscinny.cs.uni-sb.de [134.96.235.32]) by mail.cs.uni-sb.de (8.13.4/2005060800) with ESMTP id j7RBGgE4009963; Sat, 27 Aug 2005 13:16:43 +0200 (CEST) X-Authentication-Warning: mail.cs.uni-sb.de: Host goscinny.cs.uni-sb.de [134.96.235.32] claimed to be mail.st.cs.uni-sb.de Received: from [IPv6:::1] (localhost [127.0.0.1]) by mail.st.cs.uni-sb.de (Postfix) with ESMTP id 49E8F1BE22; Sat, 27 Aug 2005 13:16:42 +0200 (CEST) In-Reply-To: <20050826113400.GB5470@three-tuns.net> References: <34f22df101c14e15560de909ace48d3a@cs.uni-sb.de> <20050826113400.GB5470@three-tuns.net> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6a0d230d1d1dd537d5c33ff693437c84@cs.uni-sb.de> Content-Transfer-Encoding: 7bit Cc: Caml List From: Christian Lindig Subject: Re: [Caml-list] how to enlarge header of blocks? Date: Sat, 27 Aug 2005 13:17:40 +0200 To: Mark Shinwell X-Mailer: Apple Mail (2.622) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.1 (triton.rz.uni-saarland.de [134.96.7.25]); Sat, 27 Aug 2005 13:16:47 +0200 (CEST) X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 6.31.1.0; VDF 6.31.1.186 X-Miltered: at nez-perce with ID 43104BA1.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 43104BA0.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; lindig:01 lindig:01 caml-list:01 shinwell:01 run-time:01 run-time:01 arrays:01 garbage:01 uni-sb:01 constraints:02 crashed:04 structure:04 i'd:05 table:93 maps:06 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 Am 26.08.2005 um 13:34 schrieb Mark Shinwell: > What information do you wish to store? Rather than adjusting the block > headers, it might be possible to simply tack it onto the end as extra > fields, provided those fields obey the GC structure constraints. Currently I'd just like to store the address of the allocation site. I've tried adding an extra field, hoping that the run-time system would never access it. But either I did not get it right, or my assumptions about the run-time system were too simple. In any case, the programs crashed. I believe this had to do with the representation of arrays but no longer remember exactly. As an alternative, one could maintain a table on the side that maps the address of the block to whatever information is associated with it. But since the garbage collector moves blocks, this isn't simple to maintain, either. -- Christian