New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiler warning for _Py_InIntegralTypeRange
#97786
Comments
Reported for WebAssembly builds at #97786 . |
This avoids compiler warnings and is probably safer from undefined behavior than the previous code. Fixes pythongh-97786.
This avoids compiler warnings and is probably safer from undefined behavior than the previous code. Fixes pythongh-97786.
See also #83458. This bug was one of my motivations to add |
See also #78604. |
My abandonned attempt to fix this warning using nextafter(): PR #17933. I abandonned my PR because I didn't have time to work on it. |
cc: @mdickinson as a numeric details expert |
I had half a solution to this at one point (the |
this warning has been around a while, no rush. I just figured you're the best to understand it. clang on any platform will reproduce it. |
Fixes compiler warnings in pytime.c.
Fixes compiler warnings in pytime.c. (cherry picked from commit b1b375e2670a58fc37cb4c2629ed73b045159918) Co-authored-by: Mark Dickinson <dickinsm@gmail.com>
Bug report
Your environment
main
(3.11.0rc2 time frame)Linked PRs
The text was updated successfully, but these errors were encountered: