Regression: AOT user-script DOMXPath::evaluate() rejects or/and expressions — compile abort in dom_xpath_or_and fixture (ext/dom/xpath.c)

[PurHur]

Category

Regression: · php-src-strict · ext/dom AOT user-script bridge

Problem

DOMXPath or/and parity was fixed for VM/JIT in #32050, but AOT user-script compile still aborts for the same expressions. In this workspace, targeted AOT tests fail because DOMXPath::evaluate() rejects or/and as unsupported and exits before running the fixture.

Probed 2026-08-18 via docker wrapper.

Repro	Zend 8.2+	AOT (2026-08-18)
evaluate('true() or false()') in dom_xpath_or_and.phpt	true	compile abort: unsupported expression class
evaluate('1 or 0')	true	compile abort
count(//a[@id or @class])	2.0	compile abort before runtime

php-src reference

• php/php-src ext/dom/xpath.c — DOMXPath::query/evaluate via libxml XPath evaluator (supports XPath 1.0 boolean operators)

PHP implementation target

• ext/dom/JitDomXPathEvaluateUserScript.php — extend user-script AOT bridge to accept/compile or/and expression shapes already supported by VM/JIT path
• ext/dom/JitDomXPathExpr.php (if needed) — share boolean-expression acceptance logic; no new runtime/*.c

Repro

./script/phpunit.sh --filter 'DomXpathOrAndAotTest|AotTest::testCases.*dom_xpath_or_and'
./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && ./phpc build -o /tmp/dom_or_and test/repro/maintainer_gap_dom_xpath_or_and.php && /tmp/dom_or_and'

Done when

• dom_xpath_or_and AOT fixture compiles and matches Zend outputs (or=2, and=1, not_id=2, boolean evaluates)
• Targeted AOT + VM/JIT guards pass (DomXpathOrAndAotTest and existing VM/JIT tests)
• php-src-strict; no php-compiler-strict shortcut

[PurHur]

claim: PHP Compiler Ext — DOM & XML — starting this run

[PurHur]

Blocked on upstream AOT verifier regression in this workspace (not specific to DOMXPath).

./script/phpunit.sh --filter 'DomXpathOrAndAotTest'
# FAIL: AOT compile failed ... exit 255

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && ./phpc build -o /tmp/dom_or_and test/repro/maintainer_gap_dom_xpath_or_and.php'
# FAIL 255: Module verification failed
#   Global is referenced by parentless instruction!
#   call @__compiler_jit_raise_error(...)

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && printf "%s\n" "<?php echo \"hi\\n\";" > /tmp/hello.php && ./phpc build -o /tmp/hello_bin /tmp/hello.php && /tmp/hello_bin'
# FAIL 255 with same Module verification error

Given hello-world AOT also fails, DOM-specific AOT acceptance work for or/and cannot be verified right now. Leaving this issue claimed for follow-up once the global AOT verifier break is cleared or after rebasing onto a green base.

[PurHur]

claim: worker-lane-b — lane overflow verification (issue already green on master via #32050/#32057)

Re-verified 2026-08-18 on current master — all done-when criteria pass. Prior blocker (global AOT verifier / hello-world) is not reproducible in this workspace.

Verification:

./script/phpunit.sh --filter 'DomXpathOrAndAotTest'
# OK (1 test, 5 assertions)

./script/phpunit.sh --filter 'DomXpathOrAndVMTest|DomXpathOrAndJITTest'
# OK

./script/docker-exec.sh -- bash -lc 'php bin/vm.php test/repro/maintainer_gap_dom_xpath_or_and.php'
./script/docker-exec.sh -- bash -lc 'php bin/jit.php test/repro/maintainer_gap_dom_xpath_or_and.php'
# or=2 and=1 eval_or=true count=2.0 path_or=true (matches Zend)

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && ./phpc build -o /tmp/dom_or_and test/repro/maintainer_gap_dom_xpath_or_and.php && /tmp/dom_or_and'
# exit=0, same output as VM/JIT

Fix landed in ext/dom/JitDomXPathEvaluateUserScript.php (hasTopLevelOrAnd / tryHostEvaluateScalar) as part of #32050. Closing as verified — no additional code change required.

[PurHur]

Verified green on master — see verification comment above. Fixed by #32050 AOT or/and host-fold in JitDomXPathEvaluateUserScript.