perf: direct syscall fastpath for absolute paths in zend_virtual_cwd

[henderkes]

Absolute paths don't need to go through the per-thread cwd emulation, add a fast-path to directly hand them to libc.

since relative paths won't start with a leading slash, this adds negligible cost for them

<?php
chdir(__DIR__);

$s = microtime(true);
for ($i = 0; $i < 1000000; $i++) {
    file_exists("data.txt");
}
$rel = microtime(true) - $s;

$abs = __DIR__ . "/data.txt";
$s = microtime(true);
for ($i = 0; $i < 1000000; $i++) {
    file_exists($abs);
}
$abs_t = microtime(true) - $s;

workload	master	patch	delta
relative path	0.3521s	0.3524s	+0.09%
absolute path	0.3162s	0.2623s	−17.05%

Benchmark for Symfony demo:

compiler	route	master	vcwd-direct	delta
gcc 15	/en (home)	2741.8	2868.2	+4.61%
gcc 15	/en/blog/	1038.8	1066.5	+2.67%
clang 21	/en (home)	2740.7	2876.8	+4.97%
clang 21	/en/blog/	1031.4	1065.8	+3.34%

cc @dunglas because this will be a nice improvement for frankenphp (though fpm alike) in 8.6 :)

[staabm]

should this use php_win32_ioutil_fopen on windows?

[staabm]

ohh its ifNdef ZEND_WIN32 .. nevermind

[henderkes]

yeah, I will revisit all these small findings later on Windows

[henderkes]

Just realised that this doesn't apply to dirty composer autoloader paths with ../vendor/*. Is there any site resolving a path lexically instead of physically? If not I could drop the dot checks.

[henderkes]

The only thing I'm not entirely sure is whether we couldn't switch to using fstatat and siblings instead of doing the manual string operations for every path operation that doesn't need the resolved string.

Most importantly, ZTS (/a/c) differs from what NTS is doing (/x/c) when it could be using direct syscalls, get NTS' performance and also resolve (correctly) even for relative paths.

[henderkes]

just realized github doesn't display these lines by default in the diff - the use_realpath parameter to virtual_file_ex is passed through to tsrm_realpath_r which does:

		save = (use_realpath != CWD_EXPAND); // line 573

which disables per-component lstat/readlink. So it strips .. segments lexically and may get a different path.

Example:

/a/b/../c
/a/b is a symlink to /x
lstat/readlink resolve to /x/c
virtual_lstat resolves to /a/c