Edit report at https://bugs.php.net/bug.php?id=79034&edit=1
ID: 79034
Comment by: bugreports at gmail dot com
Reported by: bugreports at gmail dot com
Summary: PHP Fatal error: CPU doesn't support SSE2 in
Unknown on line 0
Status: Feedback
Type: Bug
Package: opcache
Operating System: Linux
PHP Version: master-Git-2019-12-26 (Git)
Block user comment: N
Private report: N
New Comment:
foregt it, it#s a gmabling machine with my code and the 3 succesful pgo builds where just random,
it's now at "CPU doesn't support SSE2" again, build without JIT for now
Previous Comments:
------------------------------------------------------------------------
[2020-01-15 18:37:14] bugreports at gmail dot com
using "lld" seems to be part of the problem
https://bugs.php.net/bug.php?id=79092 while
lld-8.0.0-1.fc30.x86_64 is used here pointed me to try without lld
- export LD="ld.lld"
+ export LD=ld.gold
---------------------------
but there is still stuff broken in the final PGO binary (latest master) while the intermdiate
"profile-gen" suceeds on the whole testsuite and that is currently reproduceable but as
said only in ta optimized "profile-use" build
TypeError: substr() expects parameter 1 to be string, null given in api_cache.php:705
line 705: if($cache_key !== NULL && substr($cache_key, 0, $hash_length) === $hash)
TypeError: substr() expects parameter 1 to be string, null given in api_cache.php:707
line 705: if($cache_key !== NULL)
line 706: {
line 707: if(substr($cache_key, 0, $hash_length) === $hash)
---------------------------
that code is part of the apcu-caching layer and follows "$inventory =
apcu_fetch('shm_inventory')" which is looped with "foreach($inventory as
$cache_key=>$shm_key)" and so move apcu out of the game don't make any sense
tar xzf /rpmbuild/SOURCES/apcu-%{apcu_version}.tgz
mv apcu-%{apcu_version} ./ext/apcu
---------------------------
sadly another build without changes didn't suceed the testsuit ebecause of random type errors
honestly i have no idea what's going on here
TypeError: strtolower() expects parameter 1 to be string, null given
------------------------------------------------------------------------
[2020-01-09 10:00:38] nikic@php.net
The referenced change is not at fault, it exposed a bug somewhere else. Unless you are interested in
debugging this issue (I can provide instructions, though the first thing to do is of course switch
to a debug build), this will only be resolved once someone qualified happens to reproduce this in
other code.
------------------------------------------------------------------------
[2020-01-09 09:28:13] bugreports at gmail dot com
PHP 8.0 MASTER is still broken, i don't get why a offending change after which a predictable
environment which worked before with 7.2/7.3/7.4/8.0 HEAD with and without JIT worked perfectly fine
has now all sort of memory curruptions and sgefaults isn't simply reverted that long
i used to build 7.2-8.0 nearly daily for weeks until that breakage
------------------------------------------------------------------------
[2019-12-31 00:02:39] bugreports at gmail dot com
tried current MASTER, still random issues, differnt runs, different errors without any change and
"Trying to access array offset on value of type array" is something not possible normally
i guess
one time even the whole test-suite passed and in the middle of the PGO-profiling spider a
demo-website segfault
-----------------------------------
removing that two lines from "php.ini" and everything is fine
opcache.jit_buffer_size = 50000000
opcache.jit = 1235
-----------------------------------
PHP Fatal error: CPU doesn't support SSE2 in Unknown on line
Trying to access array offset on value of type array
profile.sh: line 267: 322863 Segmentation fault
------------------------------------------------------------------------
[2019-12-30 12:35:26] nikic@php.net
I've fixed one JIT issue in https://github.com/php/php-src/commit/6c6d36bb94ffeefdbfacaa3fb75e1af64fbf7fe4,
but that one was introduced after the referenced commit.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=79034
--
Edit this bug report at https://bugs.php.net/bug.php?id=79034&edit=1