Optitrust GPU Phase 1: optilambda language support#34
Merged
Conversation
panther03
commented
Jan 23, 2026
panther03
commented
Jan 23, 2026
Bastacyclop
approved these changes
Jan 27, 2026
Collaborator
Bastacyclop
left a comment
Bastacyclop
left a comment
There was a problem hiding this comment.
LGTM, nice progress!
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
2 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.
TODO:
negative thread for unit test (new group axioms to be able to write a thread for inside seq for that actually requires sync? discuss)good enough without extensive tests for nowFix __gmem_get problems in clang_to_ast, and with the ThreadsCtx requirement in contractaddress this in phase2Kernel launch unit tests? (Host+ device. Currently only testing device functions in unit tests. Only test it in case studies [vector_add_gpu].)address probably in phase2 as well