Name Date Size #Lines LOC

..05-Dec-2019-

RFCs/H05-Dec-2019-

tests/H05-Dec-2019-

LICENSEH A D05-Dec-20192.7 KiB5747

Makefile.amH A D05-Dec-20192.1 KiB5532

Makefile.fragH A D05-Dec-201978 21

OBJECTS2_HOWTOH A D05-Dec-20197.1 KiB196142

README.ZEND_MMH A D05-Dec-20191.3 KiB4329

README.ZEND_VMH A D05-Dec-20194 KiB10993

ZEND_CHANGESH A D05-Dec-201936.3 KiB1,167898

Zend.dspH A D05-Dec-201912.8 KiB603449

Zend.m4H A D05-Dec-20199.2 KiB423354

ZendCore.depH A D05-Dec-20195.2 KiB259213

ZendTS.dspH A D05-Dec-201916.7 KiB733543

acconfig.hH A D05-Dec-20193.3 KiB12876

acinclude.m4H A D05-Dec-20196.1 KiB222201

bench.phpH A D05-Dec-20197.4 KiB424348

build.mkH A D05-Dec-2019871 4421

buildconfH A D05-Dec-2019676 3425

configure.inH A D05-Dec-20191 KiB5140

headerH A D05-Dec-20191.1 KiB2018

zend.cH A D05-Dec-201939.3 KiB1,3401,090

zend.hH A D05-Dec-201924 KiB786609

zend.icoH A D05-Dec-20191.3 KiB

zend_API.cH A D05-Dec-2019106.8 KiB3,6522,923

zend_API.hH A D05-Dec-201938.1 KiB722526

zend_alloc.cH A D05-Dec-201973.8 KiB2,6602,208

zend_alloc.hH A D05-Dec-201912.2 KiB265180

zend_build.hH A D05-Dec-20191.6 KiB4721

zend_builtin_functions.cH A D05-Dec-201964.4 KiB2,3491,745

zend_builtin_functions.hH A D05-Dec-20191.6 KiB407

zend_closures.cH A D05-Dec-201912.9 KiB413300

zend_closures.hH A D05-Dec-20191.8 KiB4811

zend_compile.cH A D05-Dec-2019181.4 KiB5,4534,297

zend_compile.hH A D05-Dec-201929.1 KiB788538

zend_config.nw.hH A D05-Dec-20192.4 KiB9024

zend_config.w32.hH A D05-Dec-20193 KiB10147

zend_constants.cH A D05-Dec-201914 KiB470357

zend_constants.hH A D05-Dec-20194.9 KiB8545

zend_default_classes.cH A D05-Dec-20191.7 KiB4513

zend_dynamic_array.cH A D05-Dec-20192.3 KiB7337

zend_dynamic_array.hH A D05-Dec-20191.9 KiB4815

zend_errors.hH A D05-Dec-20192.1 KiB5320

zend_exceptions.cH A D05-Dec-201927.4 KiB856620

zend_exceptions.hH A D05-Dec-20193 KiB6921

zend_execute.cH A D05-Dec-201938.9 KiB1,3271,101

zend_execute.hH A D05-Dec-201912.9 KiB423315

zend_execute_API.cH A D05-Dec-201949.6 KiB1,7371,381

zend_extensions.cH A D05-Dec-20197.2 KiB251175

zend_extensions.hH A D05-Dec-20194.5 KiB13472

zend_fast_cache.hH A D05-Dec-20194 KiB14278

zend_float.cH A D05-Dec-20191.9 KiB6536

zend_float.hH A D05-Dec-201915.3 KiB425264

zend_gc.cH A D05-Dec-201919.1 KiB740613

zend_gc.hH A D05-Dec-20197.2 KiB246183

zend_globals.hH A D05-Dec-20197.1 KiB321189

zend_globals_macros.hH A D05-Dec-20193.2 KiB10962

zend_hash.cH A D05-Dec-201935.6 KiB1,5851,271

zend_hash.hH A D05-Dec-201917 KiB388252

zend_highlight.cH A D05-Dec-20195.8 KiB238184

zend_highlight.hH A D05-Dec-20192.4 KiB6225

zend_indent.cH A D05-Dec-20194 KiB157111

zend_indent.hH A D05-Dec-20191.4 KiB386

zend_ini.cH A D05-Dec-201917.5 KiB682505

zend_ini.hH A D05-Dec-20199.8 KiB222146

zend_ini_parser.yH A D05-Dec-201910.8 KiB383278

zend_ini_scanner.cH A D05-Dec-2019101.8 KiB4,6174,440

zend_ini_scanner.hH A D05-Dec-20191.9 KiB4713

zend_ini_scanner.lH A D05-Dec-201915.8 KiB609388

zend_ini_scanner_defs.hH A D05-Dec-2019254 1411

zend_interfaces.cH A D05-Dec-201918.4 KiB601439

zend_interfaces.hH A D05-Dec-20194 KiB8137

zend_istdiostream.hH A D05-Dec-20191.6 KiB4513

zend_iterators.cH A D05-Dec-20193.2 KiB10868

zend_iterators.hH A D05-Dec-20193.6 KiB9435

zend_language_parser.yH A D05-Dec-201945.4 KiB1,011790

zend_language_scanner.cH A D05-Dec-2019170.1 KiB7,4167,126

zend_language_scanner.hH A D05-Dec-20192.4 KiB7432

zend_language_scanner.lH A D05-Dec-201949.8 KiB2,2291,758

zend_language_scanner_defs.hH A D05-Dec-2019326 1613

zend_list.cH A D05-Dec-20199.7 KiB374274

zend_list.hH A D05-Dec-20195 KiB12769

zend_llist.cH A D05-Dec-20196.8 KiB320224

zend_llist.hH A D05-Dec-20193.9 KiB8747

zend_modules.hH A D05-Dec-20195 KiB14291

zend_multibyte.cH A D05-Dec-201927.1 KiB1,181949

zend_multibyte.hH A D05-Dec-20193.7 KiB8235

zend_multiply.hH A D05-Dec-20192.5 KiB6133

zend_object_handlers.cH A D05-Dec-201943 KiB1,4071,050

zend_object_handlers.hH A D05-Dec-20198.4 KiB17775

zend_objects.cH A D05-Dec-20196.4 KiB192128

zend_objects.hH A D05-Dec-20192.2 KiB4714

zend_objects_API.cH A D05-Dec-201912.7 KiB413288

zend_objects_API.hH A D05-Dec-20194.2 KiB10055

zend_opcode.cH A D05-Dec-201913.6 KiB524427

zend_operators.cH A D05-Dec-201950.5 KiB2,0841,701

zend_operators.hH A D05-Dec-201915.4 KiB460343

zend_ptr_stack.cH A D05-Dec-20193 KiB12272

zend_ptr_stack.hH A D05-Dec-20194 KiB12271

zend_qsort.cH A D05-Dec-20193.3 KiB12878

zend_qsort.hH A D05-Dec-20191.4 KiB376

zend_sprintf.cH A D05-Dec-20191.6 KiB5015

zend_stack.cH A D05-Dec-20194 KiB175119

zend_stack.hH A D05-Dec-20192.3 KiB5923

zend_static_allocator.cH A D05-Dec-20192.6 KiB8546

zend_static_allocator.hH A D05-Dec-20191.8 KiB5620

zend_stream.cH A D05-Dec-201910.9 KiB359282

zend_stream.hH A D05-Dec-20192.9 KiB8247

zend_strtod.cH A D05-Dec-201952 KiB2,6602,202

zend_strtod.hH A D05-Dec-20191.7 KiB3813

zend_ts_hash.cH A D05-Dec-20199.5 KiB381280

zend_ts_hash.hH A D05-Dec-20196.9 KiB13673

zend_types.hH A D05-Dec-20192.3 KiB7034

zend_variables.cH A D05-Dec-20194.7 KiB208148

zend_variables.hH A D05-Dec-20193.9 KiB10760

zend_vm.hH A D05-Dec-20191.4 KiB306

zend_vm_def.hH A D05-Dec-2019132.4 KiB4,4643,797

zend_vm_execute.hH A D05-Dec-20191 MiB34,03628,860

zend_vm_execute.sklH A D05-Dec-20192.2 KiB8468

zend_vm_gen.phpH A D05-Dec-201944.4 KiB1,3471,118

zend_vm_opcodes.hH A D05-Dec-20197.7 KiB156135

README.ZEND_MM

1Zend Memory Manager
2===================
3
4General:
5--------
6
7The goal of the new memory manager (available since PHP 5.2) is to reduce memory
8allocation overhead and speedup memory management.
9
10The new manager's "configure" has no "--disable-zend-memory-manager" option,
11but it has "--enable-malloc-mm" instead.  It is enabled by default in DEBUG
12build and disabled by default in RELEASE build.  when enabled it allows selecting
13between malloc and emalloc at runtime so you can use internal and external memory
14debuggers without recompilation.
15
16Debugging:
17----------
18
19Normal:
20
21    $ sapi/cli/php -r 'leak();'
22
23Zend MM disabled:
24
25    $ USE_ZEND_ALLOC=0 valgrind --leak-check=full sapi/cli/php -r 'leak();'
26
27Shared extensions:
28------------------
29
30Since PHP 5.3.11 it is possible to prevent shared extensions from unloading so
31that valgrind can correctly track the memory leaks in shared extensions. For
32this there is the ZEND_DONT_UNLOAD_MODULES environment variable. If set, then
33DL_UNLOAD() is skipped during the shutdown of shared extensions.
34
35Tweaking:
36---------
37
38The Zend MM can be tweaked using ZEND_MM_MEM_TYPE and ZEND_MM_SEG_SIZE environment
39variables.  Default values are "malloc" and "256K". Dependent on target system you
40can also use "mmap_anon", "mmap_zero" and "win32" storage managers.
41
42	$ ZEND_MM_MEM_TYPE=mmap_anon ZEND_MM_SEG_SIZE=1M sapi/cli/php ..etc.
43

README.ZEND_VM

1ZEND_VM
2=======
3
4ZEND_VM architecture allows specializing opcode handlers according to op_type
5fields and using different execution methods (call threading, switch threading
6and direct threading). As a result ZE2 got more than 20% speedup on raw PHP
7code execution (with specialized executor and direct threading execution
8method). As in most PHP applications raw execution speed isn't the limiting
9factor but system calls and database callls are, your mileage with this patch
10will vary.
11
12Most parts of the old zend_execute.c go into zend_vm_def.h. Here you can
13find opcode handlers and helpers. The typical opcode handler template looks
14like this:
15
16ZEND_VM_HANDLER(<OPCODE-NUMBER>, <OPCODE>, <OP1_TYPES>, <OP2_TYPES>)
17{
18	<HANDLER'S CODE>
19}
20
21<OPCODE-NUMBER> is a opcode number (0, 1, ...)
22<OPCODE> is an opcode name (ZEN_NOP, ZEND_ADD, :)
23<OP1_TYPES> & <OP2_TYPES> are masks for allowed operand op_types. Specializer
24will generate code only for defined combination of types. You can use any
25combination of the following op_types UNUSED, CONST, VAR, TMP and  CV also
26you can use ANY mask to disable specialization according operand's op_type.
27<HANDLER'S CODE> is a handler's code itself. For most handlers it stills the
28same as in old zend_execute.c, but now it uses macros to access opcode operands
29and some internal executor data.
30
31You can see the conformity of new macros to old code in the following list:
32
33EXECUTE_DATA
34	execute_data
35ZEND_VM_DISPATCH_TO_HANDLER(<OP>)
36	return <OP>_helper(ZEND_OPCODE_HANDLER_ARGS_PASSTHRU)
37ZEND_VM_DISPATCH_TO_HELPER(<NAME>)
38	return <NAME>(ZEND_OPCODE_HANDLER_ARGS_PASSTHRU)
39ZEND_VM_DISPATCH_TO_HELPER_EX(<NAME>,<PARAM>,<VAL>)
40	return <NAME>(<VAL>, ZEND_OPCODE_HANDLER_ARGS_PASSTHRU)
41ZEND_VM_CONTINUE()
42	return 0
43ZEND_VM_NEXT_OPCODE()
44	NEXT_OPCODE()
45ZEND_VM_SET_OPCODE(<TARGET>
46	SET_OPCODE(<TARGET>
47ZEND_VM_INC_OPCODE()
48	INC_OPCOD()
49ZEND_VM_RETURN_FROM_EXECUTE_LOOP()
50	RETURN_FROM_EXECUTE_LOOP()
51ZEND_VM_C_LABEL(<LABEL>):
52	<LABEL>:
53ZEND_VM_C_GOTO(<LABEL>)
54	goto <LABEL>
55OP<X>_TYPE
56	opline->op<X>.op_type
57GET_OP<X>_ZVAL_PTR(<TYPE>)
58	get_zval_ptr(&opline->op<X>, EX(Ts), &free_op<X>, <TYPE>)
59GET_OP<X>_ZVAL_PTR_PTR(<TYPE>)
60	get_zval_ptr_ptr(&opline->op<X>, EX(Ts), &free_op<X>, <TYPE>)
61GET_OP<X>_OBJ_ZVAL_PTR(<TYPE>)
62	get_obj_zval_ptr(&opline->op<X>, EX(Ts), &free_op<X>, <TYPE>)
63GET_OP<X>_OBJ_ZVAL_PTR_PTR(<TYPE>)
64	get_obj_zval_ptr_ptr(&opline->op<X>, EX(Ts), &free_op<X>, <TYPE>)
65IS_OP<X>_TMP_FREE()
66	IS_TMP_FREE(free_op<X>)
67FREE_OP<X>()
68	FREE_OP(free_op<X>)
69FREE_OP<X>_IF_VAR()
70	FREE_VAR(free_op<X>)
71FREE_OP<X>_VAR_PTR()
72	FREE_VAR_PTR(free_op<X>)
73
74
75Executor's helpers can be defined without parameters or with one parameter.
76This is done with the following constructs:
77
78ZEND_VM_HELPER(<HELPER-NAME>, <OP1_TYPES>, <OP2_TYPES>)
79{
80	<HELPER'S CODE>
81}
82
83ZEND_VM_HELPER_EX(<HELPER-NAME>, <OP1_TYPES>, <OP2_TYPES>, <PARAM_SPEC>)
84{
85	<HELPER'S CODE>
86}
87
88Executor's code is generated by PHP script zend_vm_gen.php it uses zend_vm_def.h
89and zend_vm_execute.skl as input and produces zend_vm_opcodes.h and
90zend_vm_execute.h. The first file is a list of opcode definitions. It is
91included from zend_compile.h. The second one is an executor code itself. It is
92included from zend_execute.c.
93
94zend_vm_gen.php can produce different kind of executors. You can select
95different opcode threading model using --with-vm-kind=CALL|SWITCH|GOTO. You can
96disable opcode specialization using --without-specializer. You can include or
97exclude old executor together with specialized one using --without-old-executor.
98At last you can debug executor using original zend_vm_def.h or generated file
99zend_vm_execute.h. Debugging with original file requires --with-lines
100option. By default ZE2 uses the following command to generate executor:
101
102$ php zend_vm_gen.php --with-vm-kind=CALL
103
104Zend Engine II currently includes two executors during the build process, one
105is the specialized version and the other is the old one non-specialized with
106function handlers. By default Zend Engine II uses the specialized one but you
107can switch to the old executor at runtime by calling zend_vm_use_old_executor().
108
109