bench: refactor to use dynamic memory allocation in blas/ext/base/sapx

[Erennn7]

bench: refactor to use dynamic memory allocation in blas/ext/base/sapx
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: na
task: lint_javascript_cli
status: na
task: lint_javascript_examples
status: na
task: lint_javascript_tests
status: na
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: passed
task: lint_c_tests_fixtures
status: na
task: lint_shell
status: na
task: lint_typescript_declarations
status: passed
task: lint_typescript_tests
status: na
task: lint_license_headers
status: passed

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

#8643

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.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/ext/base/sapx	$\color{green}388/388$ $\color{green}+100.00%$	$\color{green}26/26$ $\color{green}+100.00%$	$\color{green}4/4$ $\color{green}+100.00%$	$\color{green}388/388$ $\color{green}+100.00%$

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