Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71406
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuSKDCS4g-Luy2QphBg0CFfGb=Dbpm0BuenRzYchAnrAWg@mail.gmail.com>
References: <d27df615bc27d701daceb5ee605f540f.squirrel@webmail.klapt.com>
	<CAMUwpuSKDCS4g-Luy2QphBg0CFfGb=Dbpm0BuenRzYchAnrAWg@mail.gmail.com>
Date: Wed, 22 Jan 2014 12:27:13 +0100
Message-ID: <CAEZPtU5+tb5dwk2V-x+rUEJuVnKay40c51=FCBYOB-TVV3RnBA@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: Anatol Belski <ab@php.net>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] 64 bit improvements, open questions
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Jan 22, 2014 at 11:56 AM, Julien Pauli <jpauli@php.net> wrote:

> I would suggest getting rid of those old SAPIs nobody use anymore.
> Late 90's SAPI that are not used/maintained anymore can die , IMO.

agreed.

> I also have a memory usage question.
> Have we measured the impact of extending all 32 ints to 64 ? Memory
> usage should be higher, but how many higher ?

For buffers (string), 4 bytes more as the length is now an integer
(always 32 bits, even on linux 64bit) and it will be size_t, which
will be 64bit from now on. No change for integers as we use long now,
which is 64bit already on 64bit systems (but windows, always 32bits
there).

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org