Received: by 10.205.122.65 with SMTP id gf1mr1143554bkc.2.1339833134103;
        Sat, 16 Jun 2012 00:52:14 -0700 (PDT)
X-BeenThere: pike-general@googlegroups.com
Received: by 10.204.128.67 with SMTP id j3ls2334055bks.9.gmail; Sat, 16 Jun
 2012 00:52:13 -0700 (PDT)
Received: by 10.204.143.145 with SMTP id v17mr1148319bku.7.1339833133763;
        Sat, 16 Jun 2012 00:52:13 -0700 (PDT)
Received: by 10.204.143.145 with SMTP id v17mr1148318bku.7.1339833133746;
        Sat, 16 Jun 2012 00:52:13 -0700 (PDT)
Return-Path: <pike-requ...@roxen.com>
Received: from mail.roxen.com (mail.roxen.com. [212.247.29.220])
        by gmr-mx.google.com with ESMTP id hy18si9003053bkc.2.2012.06.16.00.52.13;
        Sat, 16 Jun 2012 00:52:13 -0700 (PDT)
Received-SPF: pass (google.com: domain of pike-requ...@roxen.com designates 212.247.29.220 as permitted sender) client-ip=212.247.29.220;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of pike-requ...@roxen.com designates 212.247.29.220 as permitted sender) smtp.mail=pike-requ...@roxen.com; dkim=pass header...@gmail.com
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.roxen.com (Postfix) with ESMTP id 0B048628248;
	Sat, 16 Jun 2012 09:52:13 +0200 (CEST)
X-Virus-Scanned: amavisd-new at roxen.com
Received: from mail.roxen.com ([212.247.29.220])
	by localhost (marge.roxen.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id anRSv5avco5d; Sat, 16 Jun 2012 09:52:00 +0200 (CEST)
Received: by mail.roxen.com (Postfix, from userid 203)
	id D452E62824C; Sat, 16 Jun 2012 09:52:00 +0200 (CEST)
Old-Return-Path: <ros...@gmail.com>
X-Original-To: p...@roxen.com
Delivered-To: p...@roxen.com
X-Virus-Scanned: amavisd-new at roxen.com
X-Spam-Score: -3.089
X-Spam-Level: 
X-Spam-Status: No, score=-3.089 required=5 tests=[BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.5,
	T_DKIM_INVALID=0.01]
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=BH+EL8uzyu1RBLDDvKZdzIDwvO2s+8zxo2pCJOcfsFE=;
        b=d+XDCGtAfpsbNkGi7MVOXbXHYZDXoqXin7S+H0+qzBTWLwD7QCkELQDTXVmZqKJpbr
         a4QSyZG87gO+RklHH7dEiNiQnwu1miqWjfCAB7jwGD3EKJBYP3QQiswWoWx7YXPUgAye
         fG2WhPtnE+NElXdwjluNlXkRgi6LBhp270z0O8wi6caWbkx9JIvB+M8/fM40O510hsBX
         S9LLPJUTDkcdLfx5dMHtk8/PL0XRDNLOZXBxZn5XvfL4VrZAQ+FHJBwKve0+0tr9yphi
         DqcChBl2tsdIupI9nc1Uep7vSXU6PLTkEHE3L7gt50m+0jc56HFoWxqPhOpWbSvkQ6cx
         Y7sw==
MIME-Version: 1.0
In-Reply-To: <alpine.LNX.2.00.1204022313450.3642@localhost>
References: <alpine.LNX.2.00.1204022313450.3642@localhost>
Date: Sat, 16 Jun 2012 17:51:44 +1000
Message-ID: <CAPTjJmpEAQN=qci+VC-Y9fTfKagOxRGga=S7+5PKAGOTPQV...@mail.gmail.com>
Subject: Re: new block allocator
From: Chris Angelico <ros...@gmail.com>
To: Pike mailinglist <p...@roxen.com>
Content-Type: text/plain; charset=ISO-8859-1
Resent-Message-ID: <EGxUostAI7K.A.hzB.gsD...@marge.roxen.com>
Resent-From: p...@roxen.com
X-Mailing-List: <p...@roxen.com> archive/latest/13114
X-Loop: p...@roxen.com
Precedence: list
Resent-Sender: pike-requ...@roxen.com
Resent-Date: Sat, 16 Jun 2012 09:52:00 +0200 (CEST)

On Tue, Apr 3, 2012 at 7:16 AM, Arne Goedeke <e...@laramies.com> wrote:
> We pushed an experimental branch which uses a new block allocator we have
> been developing. This one uses a different algorithm than the one we briefly
> mentioned on the conference. The new one uses a hashtable for page lookup
> instead of radix trees.
>
> The branch can be found under arne/block_alloc, a GJAlloc-bundle is
> available at http://fortranland.com/GJAlloc-0.08.tar.gz or from
> https://github.com/arneg/GJAlloc via git. The branch currently contains alot
> of obsolete history, which we would squash into one commit in case of
> inclusion.

Apologies for the thread necromancy, but I'm playing around with this
new allocator and can't get it to build. I cloned GJAlloc from github,
managed to get that to build, and installed it into its chosen
location of /usr/local/lib (which is listed in /etc/ld.so.conf), and
then went to build Pike. I can compile a sample piece of code similar
to the one in src/configure, but 'make reconfigure' closes with
"WARNING:  Gjalloc could not be found, thats bad!", and running
bin/pike gives an opening message "NO PIKE_NEW_BLOCK_ALLOC".

This is using Pike on branch arne/block_alloc, and GJAlloc on branch master.

Attempting a 'make clean' and 'make' didn't change anything, neither
did re-cloning (from a local repository clone).

Any advice would be greatly appreciated.

Thanks!

Chris Angelico