Skip to content

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

Closed

Description

@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

Activity

  1. sobolevn commented on Apr 27, 2024

    @sobolevn
    Member
  2. nineteendo commented on Apr 28, 2024

    @nineteendo
    Contributor

    Any updates on this?

  3. sobolevn commented on Apr 29, 2024

    @sobolevn
    Member
  4. lysnikolaou commented on Apr 29, 2024

    @lysnikolaou
    Member

    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.

  5. corona10 commented on Apr 29, 2024

    @corona10
    Member
    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)

  6. added 2 commits that reference this issue on Apr 30, 2024
  7. corona10 commented on Apr 30, 2024

    @corona10
    Member

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

  8. nineteendo commented on Apr 30, 2024

    @nineteendo
    Contributor

    Fixed for me too.

  9. corona10 commented on Apr 30, 2024

    @corona10
    Member

    Issue fixed by #118380

  10. ZeroIntensity commented on Aug 9, 2024

    @ZeroIntensity
    Member

    This might need to get reopened. I'm encountering this error when trying to compile with the JIT on the main branch (but not 3.13, FWIW).

  11. Eclips4 commented on Aug 9, 2024

    @Eclips4
    MemberAuthor

    This might need to get reopened. I'm encountering this error when trying to compile with the JIT on the main branch (but not 3.13, FWIW).

    It's looks like a new warning, so I think it's ok to open a new issue.

  12. ZeroIntensity commented on Aug 9, 2024

    @ZeroIntensity
    Member

    Ok, will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions