Implement missing/buggy FP operations with import "BDPI". Refs #28.
#29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This implements `exp`, `log`, etc. (which were previously missing in `copilot-bluespec`) as well as `sqrt` (which was previously buggy) using Bluespec's `import "BDPI"` feature, allowing these operations to be implemented in terms of C code. While not the most performant implementations around, these are much more likely to be correct than hand-written code. We can work on improving the performance of these operations in future work.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements
exp,log, etc. (which were previously missing incopilot-bluespec) as well assqrt(which was previously buggy) using Bluespec'simport "BDPI"feature, allowing these operations to be implemented in terms of C code. While not the most performant implementations around, these are much more likely to be correct than hand-written code. We can work on improving the performance of these operations in future work.Fixes #28.