-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
feat: add succinct-zkvm
target
#138433
feat: add succinct-zkvm
target
#138433
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
succinct-zkvm
target
This comment has been minimized.
This comment has been minimized.
# | ||
# todo(succinct): remove this change that was explicity against the rules. | ||
# This just happens to work, and ideally cc-rs will fix the target parsing issue before our target is merged. | ||
cc = "=1.2.0" | ||
# cc = "=1.1.22" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Problem: you cannot bump bootstrap's cc
here in this PR. cc > 1.1.22 still has problems with target parsing issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments above in the changes, it just so happened that I had forked that version of cc-rs
and it worked. Happy to redo it with the correct version if its blocking on review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine to experiment with a forked cc
version if you need it for testing under PR CI or whatever, but we can't merge this into actual master
until this bootstrap cc
bump is reverted. As in, we unfortunately need to pin bootstrap cc version to 1.1.22. See #137460 where this was done deliberately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EDIT: ah I see, it's not blocking for review, only blocking for approval/merge.
I would recommend splitting this PR up into at least two PRs:
This is to make it easier to review because it's hard to review the mixed compiler/library changes in this one PR (compiler / library are maintained by different teams). |
@jieyouxu TYSM for getting to this so quickly. My plan here, is that given the volatile state of the
Im actually just going to make this complete disjoint from the previous |
Ah. If this is another And yeah, sorting out the current zkvm target situation would be ideal to avoid confusion and footguns in the long term.
I can't really comment on this because I'm not a library maintainer/reviewer. This is partly why I recommended doing the library parts in a separate PR, so that you can discuss the library implementation decisions with a library reviewer. |
Ok went ahead and moved everything to not rely on (mostly) any The PR is definitely bigger, so I agree with your suggestion, Ill go ahead and split up these PRs soon. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
r? compiler |
r? compiler_leads |
☔ The latest upstream changes (presumably #138448) made this pull request unmergeable. Please resolve the merge conflicts. |
Closing this in favor of separating the std library impl from adding target. |
Adds a new riscv32im target with a new os (
succinct-zkvm
).Previously, there was already a
zkvm
target which is in the process of being removed, due to this issue, which we think is the right call.This PR DOES NOT attempt to resolve the aforementioned issue for the risc0 target.