Fix C lint errors

[stdlib-bot]

C Linting Failures

Linting failures were detected in the automated lint workflow run.

Workflow Details

• Run: https://github.com/stdlib-js/stdlib/actions/runs/15501940554
• Type: C Linting
• Date: 2025-06-07 00:14:13 UTC

Error Details

lib/node_modules/@stdlib/blas/ext/base/dsnannsumors/benchmark/c/benchmark.length.c:116:41: warning: Uninitialized variable: x [uninitvar]
  v = stdlib_strided_dsnannsumors( len, x, 1, &n );
                                        ^
--
                                        ^
lib/node_modules/@stdlib/blas/ext/base/dsnannsumors/benchmark/c/benchmark.length.c:155:49: warning: Uninitialized variable: x [uninitvar]
  v = stdlib_strided_dsnannsumors_ndarray( len, x, 1, 0, &n );
                                                ^

Pull Request Instructions

• Please use the following PR title format:
  "chore: fix C lint errors (issue #<ISSUE_NUMBER>)".
• Reference this issue in the "Related Issues" section of the PR body as "resolves #<ISSUE_NUMBER>".

[Deepak91168]

Hi! 👋

Could anyone please guide me on how to reproduce this linting error locally?

I'm trying to lint the following file:
lib/node_modules/@stdlib/blas/ext/base/dsnannsumors/benchmark/c/benchmark.length.c

Also, I have a question about this line (L: 99 in lib/node_modules/@stdlib/blas/ext/base/dsnannsumors/benchmark/c/benchmark.length.c):

float x[ len ];

Since x is declared as a VLA, is the lint issue possibly due to the fact that:

In C99 and later, declaring variable-length arrays (e.g., float x[len];) can be problematic in static analysis tools because the size isn't known at compile-time, and this might cause false positives or limited analysis?

Would appreciate any clarification, related resources, or hints on how to reproduce this error or better understand the cause of this warning.

Thanks You!

[pierreforstmann]

I have looked how parent issues are solved: I understand that lint tool used is cppcheck.
But I cannot reproduce this error with cppcheck 2.4