Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71127
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.net designates 212.227.15.18 as permitted sender)
Message-ID: <52D5923E.2080009@gmx.net>
Date: Tue, 14 Jan 2014 20:38:38 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Dmitry Stogov <dmitry@zend.com>, 
 PHP Internals <internals@lists.php.net>
References: <CA+9eiLtmUgWSZhoHgXy+UfiakGHG5RuJwP6o4txVsU76fRsDpQ@mail.gmail.com>
In-Reply-To: <CA+9eiLtmUgWSZhoHgXy+UfiakGHG5RuJwP6o4txVsU76fRsDpQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Memory Manager
From: chris_se@gmx.net (Christian Seiler)

Hi there,

> (For example: may be someone would
> suggest how to avoid check for USE_ZEND_ALLOC=0 to allow system malloc()
> usage on each emalloc() call?

Rename emalloc() -> real_emalloc(), then:

.h:
extern void (*emalloc)(size_t n);

.c:
void (*emalloc)(size_t n) = real_emalloc;

startup code:

if (USE_ZEND_ALLOC is 0) {
   emalloc = malloc;
}

Probably some adjustments needed (esp. for potentially different calling
conventions, so maybe malloc() will need a small wrapper), this is just
from the top of my head.

Note: this breaks ABI compatibility on most archs (because it changes
the symbol type). But could be done independently of anything else.

Note 2: Depending on system architecture, each call to the function may
incur an additional (small) penalty. No idea how this compares to the
penalty of the if() at the start of emalloc().

Regards,
Christian