Fixed parameter mismatch in complex gemm benchmarks #489
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 patch fixes the mismatching parameters passed to GEMM (and batched derivative) benchmarks when using custom csv file and enabling the
BLAS_ENABLE_COMPLEX
cmake flag.This is originally due to the fact that complex data type GEMM expects two values for each scalar
alpha
andbeta
(real and imag parts), and thus causes invalid number of parameters (+-2) as both complex and non-complex benchmarks use the same passed csv file.The patch approach is a workaround that helps :
alpha
andbeta
.