[issue36330] Warning about a potential dead code in timemodule and Clang

Stéphane Wirtel added the comment: Hi Paul, Thank you for your explanation, I was not sure about the solution and I have just preferred to publish this issue. I don't have this issue with gcc, only with clang. -- ___ Python tracker

[issue36330] Warning about a potential dead code in timemodule and Clang

Paul Ganssle added the comment: Sorry, I should say unlikely that it should ever be *true*. It seems unlikely that there is a platform or piece of hardware on which this error would be raised. -- ___ Python tracker

[issue36330] Warning about a potential dead code in timemodule and Clang

Paul Ganssle added the comment: It does seem like the values CLOCKS_PER_SEC, _PyTime_MAX and SEC_TO_NS are all defined at compile-time, so presumably this can be a compile-time error. As currently defined, though, it seems very unlikely that this would ever be false, since _PyTime_MAX is the

[issue36330] Warning about a potential dead code in timemodule and Clang

New submission from Stéphane Wirtel : env CC="/usr/bin/clang" CCX="/usr/bin/clang" ./configure > /dev/null ;and make -j 4 > /dev/null ./Modules/timemodule.c:113:13: warning: code will never be executed [-Wunreachable-code] PyErr_SetString(PyExc_OverflowError, ^~