-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add a dependency on the bedrock2 compiler #1045
Conversation
I think you'll need to rebase on #1046 to get the CI to pass |
If you rebase on master now, this should hopefully build better |
ef8d0c4
to
5c90711
Compare
Issue 1:
Issue 2:
Very confused by this one. |
$(MAKE) --no-print-directory -C $(BEDROCK2_ROOT_FOLDER) install_bedrock2 | ||
|
||
bedrock2-compiler: bedrock2 | ||
# We have to build the compiler *including* examples to get compilerExamples/MMIO.v |
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.
Is it possible that make
doesn't like recipes that start with #
? What happens if you do
# We have to build the compiler *including* examples to get compilerExamples/MMIO.v | |
@# We have to build the compiler *including* examples to get compilerExamples/MMIO.v |
instead?
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.
Adjusted to try that. The "no rule" error is especially weird because this does build locally with make
.
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.
Same error. Fascinating.
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.
Strange. Does coq-record-update build fine for you locally? Maybe it makes sense to first fix the coq-record-update failure and then look into this failure after?
@JasonGross Do you understand what is up with coq-record-update? https://github.com/mit-plv/bedrock2/runs/4257766583?check_suite_focus=true#step:6:1477 is a succeeding run on coq master. |
I'm guessing that the trick we pull to get warning annotations at fiat-crypto/etc/ci/github-actions-make.sh Line 23 in edba07d
COQTEST somehow such that https://github.com/tchajed/coq-record-update/blob/f2467e2b614bf35913c5e2406be4d67fbd85e7a4/test-normalizer.sed#L9 is not working right? But I don't see how this is happening. I've pushed a change to master that should give us more information when the CI fails (by re-running make with VERBOSE=1 ), and will force-push a rebase of this on master to see if it helps.
|
538953f
to
d73cead
Compare
I think it's just that the bedrock2 referenced here doesn't include tchajed/coq-record-update@f2467e2 yet. |
Ah, that sounds right |
And the extra text from the debug invocation suggests that the failure message is some weird interaction between
|
457f635
to
03a7436
Compare
I've rebased this, now that the rupicola bump is merged |
CI passes, so I'm going to merge this |
This needs to be in place for an end-to-end proof of X25519. Pushing it early because I kind of suspect there'll be issues with some Coq version or another, but feel free not to merge until something actually using it is ready.
Unfortunately, the
MMIO.v
file that is extremely helpful for instantiating the compiler proof is in the compiler's "examples" folder, meaning we have to build all the examples from both bedrock2/bedrock2 and bedrock2/compiler. Could it be moved?