Modifications to avoid including "gflop/s" in the "best gflop/s" computation if the validation fails #40
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 is to fix the issue mentioned in #37.
Currently, if the result is not valid, it will still print a result and so the "best gflop/s" which is determined could be incorrect. In particular, if the CUDA kernel launch fails, the "best gflop/s" will be too big since the kernel time was very fast since the kernel didn't run. This will cause the "best flop/s" to be based on an invalid run.
This PR avoids the problem above. If the validation fails, it sets the kernel time to the biggest possible, so that it will not be considered in the computation of "best" gflop/s. There are probably cleaner ways, this is just what I was using to get it working. I'm happy to make changes if requested!