-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
[RFC] Add support for attributes on compile-time constants #16952
base: master
Are you sure you want to change the base?
Conversation
There are going to be some memory issues that CI will report, I couldn't figure those out, asked for help on the mailing list, https://news-web.php.net/php.internals/126065 |
So there are also opcache failures, not just the failures I had locally - I guess a data op isn't the right way to send a pointer to the attributes from the compilation to the runtime - I'll see if I can have it send the raw AST and delay the attribute compilation until runtime |
So for the life of me, I can't figure out why I'm unable to get the cleanup in free_zend_constant() to run properly - I added debugging code diff --git a/Zend/zend_constants.c b/Zend/zend_constants.c
index 8b92650816..ade2efb618 100644
--- a/Zend/zend_constants.c
+++ b/Zend/zend_constants.c
@@ -41,6 +41,8 @@ void free_zend_constant(zval *zv)
{
zend_constant *c = Z_PTR_P(zv);
+ fprintf(stderr, "Freeing constant %s\n", ZSTR_VAL(c->name));
+
if (!(ZEND_CONSTANT_FLAGS(c) & CONST_PERSISTENT)) {
zval_ptr_dtor_nogc(&c->value);
if (c->name) {
@@ -50,7 +52,7 @@ void free_zend_constant(zval *zv)
zend_string_release_ex(c->filename, 0);
} and none of the compile-time constants in my test script are listed as being freed, though plenty of php-provided ones are. If the cleanup is never reached, then it makes sense that the attributes are not properly freed, but why isn't the cleanup reached? |
From f411ddf4c984ed8d614d003e9eb209387b904f9b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tim=20D=C3=BCsterhus?= <[email protected]>
Date: Wed, 27 Nov 2024 17:32:48 +0100
Subject: [PATCH] Fix constant attribute leak
---
Zend/zend_execute_API.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Zend/zend_execute_API.c b/Zend/zend_execute_API.c
index 9ebc15f3a4..f4adeb855f 100644
--- a/Zend/zend_execute_API.c
+++ b/Zend/zend_execute_API.c
@@ -302,6 +302,9 @@ ZEND_API void zend_shutdown_executor_values(bool fast_shutdown)
if (c->filename) {
zend_string_release_ex(c->filename, 0);
}
+ if (c->attributes) {
+ zend_hash_release(c->attributes);
+ }
efree(c);
zend_string_release_ex(key, 0);
} ZEND_HASH_MAP_FOREACH_END_DEL();
--
2.43.0 This appears to fix the leak for me. I did not verify if it is possible to call |
Thanks - I forgot there was a second place that constants are freed, though I should have remembered it from adding |
So on circleci the deprecation messages don't seem to be properly found, and on windows there are failures with exit code 1073741819, but only for the Reflection tests |
@DanielEScherzer This is not related to CircleCI / ARM, but to JIT. You should be able to reproduce the issue locally with:
see: #11293 (comment) |
I have taken the liberty to push a fix into your PR. |
I can reproduce issues for the 3 tests that fail on Windows by using a non-debug ZTS build and running with Valgrind. Specifically when I configure as follows:
And run the tests as follows:
Running
|
RFC filed: https://wiki.php.net/rfc/attributes-on-constants |
e8f731b
to
50f88e5
Compare
Rebased to update for #17101 fix, then squashed and added UPGRADING |
50f88e5
to
819ed7e
Compare
819ed7e
to
5b65cd9
Compare
Fixed conflict from #17306 |
5b65cd9
to
6f5e5cc
Compare
Rebased to fix conflict from #17056 - @iluuu1994 do you think you might have a chance to review this soon? I see that @TimWolla requested that you take a look |
Yes, I'll review tomorrow. |
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.
You should try running with ASAN, it will reveal some failures in both Zend/tests/attributes/constants
and Zend/tests/attributes/deprecated
related to shutdown/cleanup of attributes.
#[MyAttrib(5, param: "example")] | ||
const WITH_PARAMETERS = true; | ||
|
||
echo zend_test_compile_to_ast( file_get_contents( __FILE__ ) ); |
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.
Why not just use the same assert(false && function () { ... });
approach we use everywhere?
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.
Because global constants cannot go in functions and so I couldn't find a way to test the ast export with that approach
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, but doesn't that mean that constants never appear here? And shouldn't that just mean that we don't need to implement support for this in the first place? A simple assert may do.
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 don't really understand what you mean by
A simple assert may do.
I figured that if
- since AST pretty printing exists for constant declarations, it should be accurate for constants with attributes
- since there isn't an existing way to test that pretty printing, I should add one
We could just remove the logic for ZEND_AST_CONST_DECL
from ast pretty printing entirely, but personally I find it helpful while debugging with gdb to be able to examine the ast
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.
since AST pretty printing exists for constant declarations, it should be accurate for constants with attributes
Other declarations can actually occur in assert()
though, which is the only reason they are supported.
I don't think it's a good idea to write code for a case that can't actually execute, at least if it isn't trivial, and then also requires a special testing mechanism.
but personally I find it helpful while debugging with gdb to be able to examine the ast
Note that we've recently added AST dumping from GDB, which will be more accurate and detailed.
php-src/scripts/gdb/php_gdb.py
Line 158 in dc7161c
class ZendAstPrettyPrinter(gdb.printing.PrettyPrinter): |
} | ||
} | ||
|
||
echo zend_test_compile_to_ast( file_get_contents( __FILE__ ) ); |
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.
The tests in ext/zend_test/tests/compile_to_ast don't seem related to this PR. Does this actually test something we don't have yet? See Zend/tests/enum/ast-dumper.phpt.
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.
They are not strictly related to the attributes on constants feature, but are included because I introduce zend_test_compile_to_ast()
for use in testing the attributes on constants, and figured we should also include some tests for that function directly.
Zend/zend_constants.c
Outdated
zend_file_context original_file_context; | ||
zend_file_context_begin(&original_file_context); | ||
|
||
zend_compile_attributes(&c->attributes, ast, 0, ZEND_ATTRIBUTE_TARGET_CONST, 0); |
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 don't think you should call this function at runtime. It's likely possible to call it at compile time and pass an IS_PTR
to the attribute array to op_data
of ZEND_DECLARE_ATTRIBUTED_CONST
instead.
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.
So I spent some time trying to do this again, but couldn't get it to work with a constant deprecated with itself as the message. I earlier posted that
...I guess a data op isn't the right way to send a pointer to the attributes from the compilation to the runtime - I'll see if I can have it send the raw AST and delay the attribute compilation until runtime
would it be okay to move the call to compile time as part of a follow-up, and get the main functionality merged?
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 can have a look tomorrow. The benefit of handling it in the same PR is that it makes it obvious which changes are no longer needed. But if it turns out to be too difficult we can delay.
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.
The infinite recursion problem is not unique to constants, it also occurs with class constants: https://3v4l.org/DibeG#v8.4.3 It only wasn't exposed because the tests use self::C
where the constant is comp-time, and thus it is inlined, avoiding runtime access and thus infinite recursion. /cc @TimWolla
Avoid spaces in `()` for function definitions and calls, rename tests for attributes being repeatable, drop tokenization tests
To show why the ZEND_AST_NAMED_ARG handling is needed
The ast contained in ast_copy_ref is already destroyed by zend_const_expr_to_zval(). Avoid the double free by just freeing the ast ref itself.
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.
Thanks for figuring out that the infinite recursion wasn't caused by me, and about how to pass a pointer to the runtime - once the fix for #17711 is merged I'll rebase this patch and address any remaining feedback
Zend/tests/attributes/constants/named_parameter_validation.phpt
Outdated
Show resolved
Hide resolved
This is also missing function JIT support...
|
We might require similar changes in more places.
https://wiki.php.net/rfc/attributes-on-constants