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.

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

Documenting backend upgrades needed for Store in 1.1.0 #12332

Closed
Tracked by #10922
mtreinish opened this issue May 2, 2024 · 0 comments · Fixed by #12421
Closed
Tracked by #10922

Documenting backend upgrades needed for Store in 1.1.0 #12332

mtreinish opened this issue May 2, 2024 · 0 comments · Fixed by #12421
Assignees
Labels
documentation Something is not clear or an error documentation
Milestone

Comments

@mtreinish
Copy link
Member

Let just go with documenting this for now as part of the 1.1.x final documentation, I'll convert this into an issue to track. Both as an upgrade note in the final release notes and also as a guidance in the writing a backend section of the docs.

I think for 1.2.x we can look at adding a global flag in the target for something like supports store, etc to provide a high level indicator for this kind of capability above the per instruction look ups. We'd probably need to do this into an opt-in way (so it defaults true) but I think having the capability to express this in the target is what we'll want longer term.

Originally posted by @mtreinish in #12322 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Something is not clear or an error documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants