-
Notifications
You must be signed in to change notification settings - Fork 8k
Fix GH-20319: Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment #20326
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
Open
+677
−104
Conversation
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
@arnaud-lb
arnaud-lb
changed the title
(削除) Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being released during assignment (削除ここまで)
(追記) Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment (追記ここまで)
Oct 29, 2025
@arnaud-lb
arnaud-lb
force-pushed
the
gh20319
branch
2 times, most recently
from
October 29, 2025 15:01
572d766 to
5f2757d
Compare
...ssignment In ASSIGN_DIM_OP, side effects of coercion may release the array or make the dimension pointer invalid (by reallocating the array). Increasing the array's refcount around the binary op is enough to prevent both issues. In ASSIGN_OP, if the variable is a reference, side effects may release it. Again, increasing the refcount prevents this.
@arnaud-lb
arnaud-lb
force-pushed
the
gh20319
branch
from
October 29, 2025 15:01
5f2757d to
e5e8392
Compare
@arnaud-lb
arnaud-lb
changed the title
(削除) Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment (削除ここまで)
(追記) Fix GH-GH-20319: Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment (追記ここまで)
Oct 30, 2025
@arnaud-lb
arnaud-lb
changed the title
(削除) Fix GH-GH-20319: Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment (削除ここまで)
(追記) Fix GH-20319: Prevent ASSIGN_OP / ASSIGN_DIM_OP lvalue from being invalidated during assignment (追記ここまで)
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
In ASSIGN_DIM_OP, side effects of coercion may release the array or make the dimension pointer invalid (by reallocating the array). Increasing the array's refcount around the binary op is enough to prevent both issues.
In ASSIGN_OP, if the variable is a reference, side effects may release it. If the variable is a var-var slot, it may be invalidated if the symbol table is resized. In the former case, increase the refcount around the binary op. In the latter, turn the slot into a reference so we can apply the same fix.
Fixes: GH-20319
Related: GH-15938