Repository navigation
Changed OverflowError condition of fast ascii converter to >= |HUGE_VAL| - #9738
Conversation
olebole
left a comment
There was a problem hiding this comment.
This is exactly the change @dhomeier suggested before. I successfully tested this on our i386 architecture. What I did not test yet is whether it does harm on other platforms; however it looks simple enough for me.
I am planning to upload the RC2 plus this patch to Debian experimental later today (CET), so if a definitive confirmation for all our platforms is needed, I can give that only tomorrow.
hamogu
left a comment
There was a problem hiding this comment.
This is way beyond my C knowledge, but I don't see how this change could do any harm, so I'm fine with including it since it seems to work.
I feel it's not necessary? 🤷♀ |
|
Thanks @dhomeier! |
Changed OverflowError condition of fast ascii converter to >= |HUGE_VAL|
|
It is already closed, but I just wanted to confirm that this does not harm on our other platforms ;-) |
Addressing #9694 - if we are right about the fast C converter internally calculating in 80 bit on some architectures like x86_64/gcc 9.2 (see discussion there), this will still raise an
OverflowErrorwhen the returned value exceedsnp.float64range (and becomesinf).Fix #9694