[TLE] Add optional offset parameter to tle.remote op#732
Open
lzllx123 wants to merge 13 commits into
Open
Conversation
…t offset for cluster/node spaces
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
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.
Overview
Add an optional scalar
i64offset parameter to thetle.remoteop on the triton v3.6.x branch, allowing device-space remote pointers to access peer memory at a specified byte offset.Changes
i64offset parameter totle.remote.i64values only.TT_IntLikefor theRemotePointersOpoffset operand to align with the verifier.RemotePointersOpverifier.test_tle_distributed_d2d.pyto demonstrate the newoffsetparameter intle.remote.