| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Same optimization as in #132849 (comment)
Sorry, something went wrong.
There was a problem hiding this comment.
I needed to use UNPACK_SEQUENCE(_TWO)_TUPLE here since it is currently the only uop that propagates the tuple items to the result.
Sorry, something went wrong.
There was a problem hiding this comment.
Nice observation. Seems like _BINARY_OP_SUBSCR_TUPLE_INT could be taught how to do this pretty easily for a constant RHS. Want to add that to your queue?
Sorry, something went wrong.
There was a problem hiding this comment.
It's already in the queue 😄
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
CALL_TUPLE_1 is equivalent to tuple(...).
Very similar to previous work on splitting up CALL_TYPE_1: #132419
This splits the instruction into a smaller instruction + 2 guards which can be optimized away. This also sets the return type to tuple.