-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix GH-16186: Ignore scope when compiling closure in non-tracing jit #16200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--TEST-- | ||
GH-16186 001 (Non-tracing JIT uses Closure scope) | ||
--EXTENSIONS-- | ||
opcache | ||
--INI-- | ||
opcache.enable=1 | ||
opcache.enable_cli=1 | ||
opcache.jit_buffer_size=64M | ||
opcache.jit=0234 | ||
opcache.file_update_protection=0 | ||
opcache.revalidate_freq=0 | ||
opcache.protect_memory=1 | ||
--FILE-- | ||
<?php | ||
|
||
class A { | ||
private $x; | ||
public function getIncrementor() { | ||
return function() { $this->x++; }; | ||
} | ||
} | ||
$a = new A(); | ||
$f = $a->getIncrementor(); | ||
$c = new stdClass(); | ||
$f(); | ||
$f2 = Closure::bind($f, $c); | ||
$f2(); | ||
$f2(); | ||
|
||
var_dump($c); | ||
|
||
?> | ||
--EXPECTF-- | ||
Warning: Undefined property: stdClass::$x in %s on line %d | ||
object(stdClass)#%d (1) { | ||
["x"]=> | ||
int(2) | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--TEST-- | ||
GH-16186 002 (Non-tracing JIT uses Closure scope) | ||
--EXTENSIONS-- | ||
opcache | ||
--INI-- | ||
opcache.enable=1 | ||
opcache.enable_cli=1 | ||
opcache.jit_buffer_size=64M | ||
opcache.jit=0214 | ||
opcache.file_update_protection=0 | ||
opcache.revalidate_freq=0 | ||
opcache.protect_memory=1 | ||
--FILE-- | ||
<?php | ||
|
||
class A { | ||
private $x; | ||
public function getIncrementor() { | ||
return function() { $this->x++; }; | ||
} | ||
} | ||
$a = new A(); | ||
$f = $a->getIncrementor(); | ||
$c = new stdClass(); | ||
$f(); | ||
$f2 = Closure::bind($f, $c); | ||
$f2(); | ||
$f2(); | ||
|
||
var_dump($c); | ||
|
||
?> | ||
--EXPECTF-- | ||
Warning: Undefined property: stdClass::$x in %s on line %d | ||
object(stdClass)#%d (1) { | ||
["x"]=> | ||
int(2) | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about
ZEND_FUNC_JIT_ON_PROF_REQUEST
?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it here initially, but I then I figured that it was not necessary because we never compile closures in
ZEND_FUNC_JIT_ON_PROF_REQUEST
mode (according to my understanding ofzend_jit_check_funcs()
). In theory we could compile closures inzend_jit_check_funcs()
by also iterating overop_array->dynamic_func_defs
, but in this case we would get the rightop_array
, so fetching it fromjit_extension
would not be necessary.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.