gh-131798: JIT: Assign type to sliced string/list/tuple #134671
Merged
+55
−3
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
eendebakpt
reviewed
May 25, 2025
| // Slicing a string/list/tuple always returns the same type. | ||
| PyTypeObject *type = sym_get_type(container); | ||
| if (type == &PyUnicode_Type || | ||
| type == &PyList_Type || |
There was a problem hiding this comment.
Suggested change
| type == &PyList_Type || | |
| type == &PyBytes_Type || | |
| type == &PyList_Type || |
I do not know whether slicing a bytes object occurs often enough to add PyBytes_Type here (and whether the jit slows down if we add more cases here), but if I understand correctly slicing bytes (or bytearray) results in a bytes (or bytearray) so we could add them.
There was a problem hiding this comment.
@fluhus, this PR is probably fine for now, but feel free to add other sequence types like this in a follow-up PR (with tests)!
brandtbucher
approved these changes
Jun 5, 2025
| for i in range(n): | ||
| false = i == TIER2_THRESHOLD | ||
| empty = "X"[:false] | ||
| empty += "" # Make JIT realize this is a string. |
| // Slicing a string/list/tuple always returns the same type. | ||
| PyTypeObject *type = sym_get_type(container); | ||
| if (type == &PyUnicode_Type || | ||
| type == &PyList_Type || |
There was a problem hiding this comment.
@fluhus, this PR is probably fine for now, but feel free to add other sequence types like this in a follow-up PR (with tests)!
brandtbucher
reviewed
Jun 6, 2025
lkollar
pushed a commit
to lkollar/cpython
that referenced
this pull request
Jun 19, 2025
Pranjal095
pushed a commit
to Pranjal095/cpython
that referenced
this pull request
Jul 12, 2025
taegyunkim
pushed a commit
to taegyunkim/cpython
that referenced
this pull request
Aug 4, 2025
Agent-Hellboy
pushed a commit
to Agent-Hellboy/cpython
that referenced
this pull request
Aug 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Slicing a string/list/tuple always returns the same type.
Make the optimizer assign a string/list/tuple type to the result of slicing a string/list/tuple.
@brandtbucher