You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
_Py_ExecutorDetach undefined when configured with --enable-experimental-jit=yes #131488
My latest pull on main (~20:00 Central Daylight Time) broke my typical build. Configuring with no arguments works, but configuring with --enable-experimental-jit=yes causes a compilation error in Object/codeobject.c
gcc -c -fno-strict-overflow -Wsign-compare -Wunreachable-code -DNDEBUG -g -O3 -Wall -D_Py_TIER2=1 -D_Py_JIT -std=c11 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wstrict-prototypes -Werror=implicit-function-declaration -fvisibility=hidden -Werror=unguarded-availability -I./Include/internal -I./Include/internal/mimalloc -I. -I./Include -DPy_BUILD_CORE -o Objects/codeobject.o Objects/codeobject.c
Objects/codeobject.c:1700:13: error: call to undeclared function '_Py_ExecutorDetach'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1700 | _Py_ExecutorDetach(co->co_executors->executors[i]);
| ^
1 error generated.
make: *** [Objects/codeobject.o] Error 1
Activity
brandtbucher commentedon Mar 20, 2025
I have a hunch this is due to the massive header refactoring over in GH-131238. JIT CI probably isn't running on those PRs.
smontanaro commentedon Mar 20, 2025
Yes, I got that impression skimming
git log(without drilling down on the exact cause). It's no big deal for me. Just reporting the issue.smontanaro commentedon Mar 20, 2025
Seems to be working (compiling and passing tests) once again.