php-in-php: JIT IncludePathRuntime — route include_path builtins through VmFs PHP not LLVM globals (#1492)

[PurHur]

Category

php-in-php · JIT/AOT lowering migration

Problem

VM get_include_path() / set_include_path() / restore_include_path() / stream_resolve_include_path() use PHP builtins in ext/standard/ + lib/Web/IncludePathResolver.php.

JIT/AOT duplicates include-path stack semantics in lib/JIT/Builtin/IncludePathRuntime.php and lib/JIT/Builtin/Type.php (__compiler_get_include_path, __compiler_set_include_path, __compiler_restore_include_path, __compiler_stream_resolve_include_path, phpc_include_path_* LLVM globals).

This diverges from VM behavior and blocks shrinking the C/LLVM runtime per #1492.

php-src reference (semantics)

• php/php-src ext/standard/basic_functions.c — php_set_include_path() / php_get_include_path()
• php/php-src ext/standard/streams.c — php_stream_resolve_include_path()
• This repo VM: ext/standard/get_include_path.php, set_include_path.php, restore_include_path.php, stream_resolve_include_path.php, lib/Web/IncludePathResolver.php

Repro

<?php
$old = get_include_path();
set_include_path($old . PATH_SEPARATOR . '/tmp');
var_export(str_contains(get_include_path(), '/tmp'));
echo "\n";
restore_include_path();
var_export(get_include_path() === $old);
echo "\n";
var_export(stream_resolve_include_path('compile_driver.php') !== false);
echo "\n";

php bin/vm.php repro_include_path.php
php bin/jit.php repro_include_path.php

Engine	Expected
Zend	true, true, bool per CWD
VM	matches Zend
JIT today	may diverge — uses IncludePathRuntime LLVM stack

Scope

Layer	Path
Shrink	lib/JIT/Builtin/IncludePathRuntime.php — delete LLVM stack impl
JIT	Route through JitResolveIncludePath / builtin jit() on ext/standard/*include_path*.php
Shared	lib/Web/IncludePathResolver.php — single SSOT for VM+JIT
AOT	link PHP helpers, not phpc_include_path_* globals

Done when

• JIT include_path builtins match VM/php-src on repro
• stream_resolve_include_path() JIT uses same resolver as VM
• PR cites lines removed from IncludePathRuntime.php / Type.php LLVM registrations
• ./script/ci-fast.sh --filter include_path green (or add compliance guard)

Related

• Epic: Self-host critical path — compiler compiles itself (M3→M5) #1492 · Stdlib: get_include_path() / set_include_path() / restore_include_path() — include path stack (bootstrap) #3223 / Stdlib: stream_resolve_include_path() — include_path filename resolution missing (ext/standard/streams.c) #6051 (include_path VM) · php-in-php: VmFsReadNative — pure PHP file_get_contents path without libc open/read FFI (#1492) #8920 (file_get_contents PHP path)

[PurHur]

claim: PHP Runtime → PHP — starting this run.

[PurHur]

Merged via #10789.

PHP path: ext/standard/IncludePathJitHelper.php (stack) + IncludePathResolveJitHelper.php (resolve); IncludePathRuntime.php is now thin LLVM bridges (no phpc_include_path_* globals, no libc access/realpath resolve loop).

Verification:

• ./script/docker-exec.sh php vendor/bin/phpunit --filter 'IncludePathRuntime|StreamResolveIncludePath' — OK (7 tests)
• ./script/docker-exec.sh php vendor/bin/phpunit --filter 'JITTest::testCases.*stream_resolve_include_path_jit' — OK
• Issue repro test/repro/include_path_9245.php — VM + JIT both print true / true / false