-
Notifications
You must be signed in to change notification settings - Fork 2
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
Is there a license on the benchmarks? #1
Comments
And a minor question—should I file bugs if I find them? For example, |
Since this is an interval project and we pre-generated the data for consistency, we didn't have the issue of g+h=0. However, if you think this is an issue, just send a pull request and i will merge them |
If we can get this repository MIT licensed, I'll work on adding it to FPBench. Are the expressions in the paper the ones you think should be merged into FPBench? Or would you rather merge all of them? |
I already gave this repo a mit license. There's no need to merge all of them. As mentioned, the composition expression 1 which made filib++ producing inconsistent result on different platform might be interesting to add to benchmark |
When @shoaibkamil gave a talk at the FPBench Community Meetings, he and I briefly discussed merging the benchmarks here into FPBench. Naturally a bunch are already in FPBench, but there are a bunch of extra ones here. However, I have a few questions / blockers on this:
methods.hpp
file?exprN
expressions? What's the level of detail you could give about these tools? (Is it at least safe to say they are doing "graphics"?) Are theextra_functionN
benchmarks randomly generated by the generator in this repo? We could add this to the metadata.exprN
benchmarks, don't include the ones that are just one function, maybe include theextra_functionN
benchmarks. I'm willing to include randomly generated benchmarks if there's some sense they were filtered & selected, or important for reproducibility, or something like that.The text was updated successfully, but these errors were encountered: