New warning: ``assignment to ‘_PyInterpreterFrame *’ from incompatible pointer type ‘_Py_UopsSymbol *’ [-Wincompatible-pointer-types]``

[Eclips4]

Bug report

Bug description:

Popped up in https://github.com/python/cpython/pull/118334/files and https://github.com/python/cpython/pull/118338/files

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-118343: (void *) casting to avoid gcc-14 build failure issue #118430

[sobolevn]

Happens in Python/optimizer_cases.c.h

[nineteendo]

Any updates on this?

[sobolevn]

cc @markshannon 3e06c7f

[lysnikolaou]

FWIW, for those with setups where warnings are treated as errors (my Fedora does this, not sure why the defaults are different), one can do CFLAGS="-Wno-error=incompatible-pointer-types" make as a work-around until this is solved.

[corona10]

Python/optimizer_cases.c.h: In function ‘optimize_uops’:
Python/optimizer_cases.c.h:1444:23: error: assignment to ‘_PyInterpreterFrame *’ from incompatible pointer type ‘_Py_UopsSymbol *’ [-Wincompatible-pointer-types]
 1444 |             gen_frame = sym_new_not_null(ctx);
      |                       ^
make: *** [Makefile:3018: Python/optimizer_analysis.o] Error 1
make: *** Waiting for unfinished jobs....

Build failure with my Fedora 40.
(gcc14)

[corona10]

The build failure is due to gcc 14 changed policy
Similar issue: https://forums.developer.nvidia.com/t/nvidia-modules-build-failure-with-upcoming-gcc-14-and-recent-kernels-due-to-misfiring-conftest-sh-test-heads-up/279072

[corona10]

Now on the Fedora 40, I am able to build with gcc-14, @lysnikolaou is it still reproduced?

[nineteendo]

Fixed for me too.

[corona10]

Issue fixed by #118380