using pointer to the tsrm ls cache instead of a function call

yet another approach

revert the local speedup approach

approach local pointers in performance sensitive areas

cleanup TSRMLS_FETCH

reworked the patch, less new stuff but worky

TLS is already used in TSRM, the way exporting the tsrm cache through
a thread local variable is not portable. Additionally, the current

reworked the patch, less new stuff but worky

TLS is already used in TSRM, the way exporting the tsrm cache through
a thread local variable is not portable. Additionally, the current
patch suffers from bugs which are hard to find, but prevent it to
be worky with apache. What is done here is mainly uses the idea
from the RFC patch, but

- __thread variable is removed
- offset math and declarations are removed
- extra macros and definitions are removed

What is done merely is

- use an inline function to access the tsrm cache. The function uses
the portable tsrm_tls_get macro which is cheap
- all the TSRM_* macros are set to placebo. Thus this opens the way
remove them later

Except that, the logic is old. TSRMLS_FETCH will have to be done once
per thread, then tsrm_get_ls_cache() can be used. Things seeming to be
worky are cli, cli server and apache. I also tried to enable bz2
shared and it has worked out of the box. The change is yet minimal
diffing to the current master bus is a worky start, IMHO. Though will
have to recheck the other previously done SAPIs - embed and cgi.

The offsets can be added to the tsrm_resource_type struct, then
it'll not be needed to declare them in the userspace. Even the
"done" member type can be changed to int16 or smaller, then adding
the offset as int16 will not change the struct size. As well on the
todo might be removing the hashed storage, thread_id != thread_id and
linked list logic in favour of the explicit TLS operations.

show more ...

native tls initial patch

make the return value more logic

as if clz() were returning 32 on empty size

make use of intrinsics available with VS for bitset lookups

Expose zend_safe_address() and use it in zend_arena_calloc()

better error messages in ZMM on Windows

emalloc() must not return NULL

Fixed comments and removed useless code.

Revert "Move safe_address into zend_multiply.h"

This reverts commit 43b02e169c718335a82b8c90c3252194f988659a.

I'm getting symbol resolution issues for zend_error_noreturn in the

Revert "Move safe_address into zend_multiply.h"

This reverts commit 43b02e169c718335a82b8c90c3252194f988659a.

I'm getting symbol resolution issues for zend_error_noreturn in the
opcache.so, so reverting this for now.

show more ...

Move safe_address into zend_multiply.h

This allows reuse in zend_arena_calloc.

Also renamed the function to zend_safe_address as it's no longer
private to the allocator.

fix number format

fixed bitset computing on win64 build

Fixed zero-size allocation in debug build

temporary fix for win64

Replaced Zend Memory Manager

several signature and data type fixes

master renames phase 3

master renames phase 2

master renames phase 1

further fixes on core

first shot on merging the core fro the int64 branch