New submission from Thomas Wouters <[email protected]>:
Objects/complexobject.c's complex_pow uses undefined behaviour, by casting a
float of unknown magnitude to a long:
int_exponent = (long)exponent.real;
At Google we build with clang and -fsanitize=float-cast-overflow by default,
which catches this particular kind of undefined behaviour. We didn't notice,
however, because the only code we've come across that exercises this behaviour
was a commented-out test in test_complex, which was uncommented in 3.8. Running
the test, or just '1e19+1j ** 1e19', is enough to trigger the undefined
behaviour. I'll prepare a PR to fix it.
----------
assignee: twouters
messages: 397947
nosy: gregory.p.smith, twouters
priority: normal
severity: normal
status: open
title: Undefined behaviour in Objects/complexobject.c's complex_pow
type: behavior
versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue44698>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
