Found in this buildbot log.

I don't see uninitialized newargs in warnings.

Python/ceval.c: In function '_PyEvalFramePushAndInit_Ex':
Python/ceval.c:1899:38: warning: 'stack_array' may be used uninitialized [-Wmaybe-uninitialized]
 1899 |     _PyInterpreterFrame *new_frame = _PyEvalFramePushAndInit(
      |                                      ^~~~~~~~~~~~~~~~~~~~~~~~
 1900 |         tstate, func, locals,
      |         ~~~~~~~~~~~~~~~~~~~~~         
 1901 |         newargs, nargs, kwnames, previous
      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 1902 |     );
      |     ~                                 
Python/ceval.c:1822:1: note: by argument 4 of type 'const _PyStackRef *' to '_PyEvalFramePushAndInit' declared here
 1822 | _PyEvalFramePushAndInit(PyThreadState *tstate, _PyStackRef func,
      | ^~~~~~~~~~~~~~~~~~~~~~~
Python/ceval.c:1868:17: note: 'stack_array' declared here
 1868 |     _PyStackRef stack_array[8];
      |                 ^~~~~~~~~~~

I gathered that the error is because the compiler does not know if stack_array would ever be used to initialize newargs, and therefore assumed it might remain uninitialized by the time it's passed to _PyEvalFramePushAndInit. Maybe I am wrong?

You can call the buildbot !buildbot Raspbian (Or !buildbot ARM64 Raspbian though that may call all ARM64 buildbots too?) to verify.

There is already this issue #132314 and PR #132376 for this false-positive warning.

I clicked the Update button accidentally somehow.

The pr proposed 2 different approaches, what do you think about this one?

I do not think that your approach here can silence the maybe uninitialized warning on stack_array. Which is a false-positive and I still think it should be silenced using a diagnostic pragma, which PR #132376 is already taking care about.

@chris-eibl The other PR seems to have been forgotten, I propose we just ignore as normal then.

Yeah, after all, your approach here deals just with clang, which is the only compiler that issues the warning so far, so most probably no need to go with something like _Py_COMP_DIAG_IGNORE_MAYBE_UNINITIALIZED.

Is it right that this is attached to gh-132314? if so, please add that issue number.

deals just with clang

Ups, I was too fast: in the issue and in your referred log

Found in this buildbot log.

gcc is raising this warning ...

@chris-eibl We have to move it, it did not work, see log.