Skip to content

Conversation

@AdamGlustein
Copy link
Collaborator

GH Actions runners updated gcc from 13.3 to 14.3 which caused the scheduled build to failure. Two changes:

  1. It looks like gcc 14.3 has an errant warning on CSP objects when calling Py_TYPE( self ) in destructor/free functions. The function is inlined and accesses the ob_type member of the object, but the compiler thinks the object has been destroyed since we called its destructor on the line above. Example:
In function 'PyTypeObject* Py_TYPE(PyObject*)',
    inlined from 'void csp::python::PyStruct_dealloc(PyStruct*)' at /data01/home/ag11460/user/github/csp/cpp/csp/python/PyStruct.cpp:771:5:
/data01/home/ag11460/y/envs/csp/include/python3.12/object.h:220:16: error: '*(PyObject*)self._object::ob_type' is used uninitialized [-Werror=uninitialized]
  220 |     return ob->ob_type;
      |                ^~~~~~~
  1. Need to explicitly include the algorithm header in gcc14

@AdamGlustein AdamGlustein added the part: build Issues and PRs related to the build process label Jul 24, 2025
svatasoiu
svatasoiu previously approved these changes Jul 24, 2025
Signed-off-by: Adam Glustein <adam.glustein@point72.com>
@AdamGlustein AdamGlustein merged commit ce58f98 into main Jul 24, 2025
27 checks passed
@AdamGlustein AdamGlustein deleted the gcc-14.3 branch July 24, 2025 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

part: build Issues and PRs related to the build process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants