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 global variables in Python bindings #1153

Open
2 of 3 tasks
RyanGlScott opened this issue Mar 25, 2021 · 1 comment
Open
2 of 3 tasks

Support LLVM global variables in Python bindings #1153

RyanGlScott opened this issue Mar 25, 2021 · 1 comment
Labels
priority High-priority issues subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm subsystem: saw-python Related to the Python bindings for the RPC SAW server subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings type: feature request Issues requesting a new feature or capability
Milestone
2025T1

Comments

@RyanGlScott
Copy link
Contributor

RyanGlScott commented Mar 25, 2021 •
edited
Loading

As far as I can tell, the Python bindings currently do not support LLVM global variables. To fully support them, I think we would need to implement the Python equivalents of the following three SAWScript functions:

  • llvm_global
  • llvm_global_initializer
  • llvm_alloc_global

Implementing bindings for llvm_global and llvm_global_initializer should be straightforward, as the SAW remote API already supports it. The SAW remote API does not currently support llvm_alloc_global, however, so more thought would need to be given for how to implement that properly. For my personal use case, I could get by with just llvm_global.
@RyanGlScott RyanGlScott added subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings labels Mar 25, 2021
RyanGlScott added a commit that referenced this issue Mar 26, 2021
@RyanGlScott
Implement global_lvalue and global_initializer in Python bindings
6462adf 
This checks off the first two bullet points of #1153. The third bullet point,
related to `llvm_alloc_global`, is left as future work.
@RyanGlScott RyanGlScott mentioned this issue Mar 26, 2021
Merged
RyanGlScott added a commit that referenced this issue Mar 26, 2021
@RyanGlScott
Implement global_var and global_initializer in Python bindings
45ca9fd 
This checks off the first two bullet points of #1153. The third bullet point,
related to `llvm_alloc_global`, is left as future work.
RyanGlScott added a commit that referenced this issue Mar 26, 2021
@RyanGlScott
Implement global_var and global_initializer in Python bindings
6332af5 
This checks off the first two bullet points of #1153. The third bullet point,
related to `llvm_alloc_global`, is left as future work.
@atomb atomb added the priority High-priority issues label May 20, 2021
@atomb atomb self-assigned this May 20, 2021
@atomb atomb removed their assignment Oct 19, 2021
@pnwamk
Copy link
Contributor

pnwamk commented Nov 18, 2021

#1517 should fix the last item

@sauclovian-g sauclovian-g added type: feature request Issues requesting a new feature or capability subsystem: saw-python Related to the Python bindings for the RPC SAW server labels Oct 30, 2024
@sauclovian-g sauclovian-g added this to the 2025T1 milestone Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority High-priority issues subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm subsystem: saw-python Related to the Python bindings for the RPC SAW server subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings type: feature request Issues requesting a new feature or capability
Projects
None yet
Milestone
2025T1
Development

No branches or pull requests
4 participants
@atomb @RyanGlScott @pnwamk @sauclovian-g