Open
Conversation
This new flag allows to run, within Criterion, binaries compiled previously by cargo or rustc.
MasterEnoc
changed the title
abolfazlabdighasmi
approved these changes
Aug 18, 2024
|
I would also greatly benefit from this. I would like to be able to compile the benchmark binary for a specific target to test performance of different embedded hardware. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently there is no way to run benchmarks without Cargo, which is awful since there is no way to benchmark binaries for projects that do not use Cargo This new flag allows to run and bench compiled binaries (linked to the criterion crate).
P.S. With "compiled binaries" I mean criterion benchmarks compiled using
rustcand linked with the criterion crate.