Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support llvm_cast_pointer in Python bindings #1575

Open
RyanGlScott opened this issue Feb 9, 2022 · 1 comment
Open

Support llvm_cast_pointer in Python bindings #1575

RyanGlScott opened this issue Feb 9, 2022 · 1 comment
Labels
subsystem: saw-python Related to the Python bindings for the RPC SAW server tech debt Issues that document or involve technical debt type: feature request Issues requesting a new feature or capability
Milestone
2025T1

Comments

@RyanGlScott
Copy link
Contributor

#1564 adds support for llvm_cast_pointer in SAWScript and the remote API, but we still need to expose Python bindings that make use of the remote API.
@RyanGlScott RyanGlScott added the subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings label Feb 9, 2022
@robdockins
Copy link
Contributor

When #1576 lands, we will also need to expose bindings corresponding to llvm_union.

@sauclovian-g sauclovian-g added tech debt Issues that document or involve technical debt type: feature request Issues requesting a new feature or capability subsystem: saw-python Related to the Python bindings for the RPC SAW server and removed subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings labels Nov 2, 2024
@sauclovian-g sauclovian-g added this to the 2025T1 milestone Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
subsystem: saw-python Related to the Python bindings for the RPC SAW server tech debt Issues that document or involve technical debt type: feature request Issues requesting a new feature or capability
Projects
None yet
Milestone
2025T1
Development

No branches or pull requests
3 participants
@RyanGlScott @robdockins @sauclovian-g