test: add test cases for blas/base/dgemm

[ShabiShett07]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: na
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

none

Description

What is the purpose of this pull request?

This pull request:

• This adds test cases to check stride of matrix C for blas/base/dgemm

Related Issues

Does this pull request have any related issues?

This pull request:

• none

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/dgemm	$\color{green}826/826$ $\color{green}+100.00\%$	$\color{green}118/118$ $\color{green}+100.00\%$	$\color{green}8/8$ $\color{green}+100.00\%$	$\color{green}826/826$ $\color{green}+100.00\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

@ShabiShett07 None of these changes are desired. You need to understand a bit more how strided storage works. Zero strides can be useful, as they allow multiple matrix elements to refer to the same underlying storage element. That means, e.g., if both strideA1 and strideA2 are both 0, I can represent an NxN matrix in which every element is 5 with a single data buffer element. Hence, zero strides allow for compact storage.

When a matrix is read-only (and not written to), this sort of compact storage is beneficial, as it allows broadcasting values without needing to allocate memory and perform physical copies.

For dgemm, the only matrix which should have the strideX != 0 prohibition is C. Your checks for strideA* and strideB* should, however, all be removed.

[ShabiShett07]

ok, I am still not clear about that, but I will remove things for A and B. I will take a look at what is desired and then understand the things

[ShabiShett07]

@kgryte, removed checks for matrix A and B