bench: refactor to use dynamic memory allocation in blas/ext/base/drrss#9285
Conversation
…hmark2 Signed-off-by: thzthix <seohas0428@naver.com>
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
Coverage Report
The above coverage report was generated for the changes in this PR. |
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
blas/ext/base/drrss
Progresses #8643 .
Description
This pull request:
blas/ext/base/drrssto use dynamic memory allocation instead of static allocation for large arrays, following the guidance in [RFC]: replace static memory allocation of large arrays in C benchmarks with dynamic memory allocation (tracking issue) #8643.Related Issues
This pull request has the following related issues:
Questions
No.
Other
Changes
double x[len]withdouble *x = malloc(len * sizeof(double))double y[len]withdouble *y = malloc(len * sizeof(double))free(x)andfree(y)calls after benchmark executionbenchmark1andbenchmark2functionsChecklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
{{TODO: add disclosure if applicable}}
@stdlib-js/reviewers