as far as I know, limiting to 16 bit exponents for _input_ was introduced to prevent undetected overflows; it must be one of the tickets
https://www.singular.uni-kl.de:8005/trac/ticket/630 https://www.singular.uni-kl.de:8005/trac/ticket/631 https://www.singular.uni-kl.de:8005/trac/ticket/696 https://www.singular.uni-kl.de:8005/trac/ticket/698 see commits in February 2015, like https://github.com/Singular/Sources/commit/fc77091687ca4452f82b084b30f8522dec3b357d There is a history of overflow issues in Singular, for example see https://www.singular.uni-kl.de:8005/trac/ticket/232 https://www.singular.uni-kl.de:8005/trac/ticket/414 Thus I suspect (without proof) that it is still possible to construct various examples leading to overflows in the results. So can someone try to find new(unknown) overflow issues in recent Singular? Jakob Am Dienstag, 11. Oktober 2016 09:33:57 UTC+2 schrieb Jean-Pierre Flori: > > Yes it is a feature of the Singular 4 update that Singular and Sage work > by default with 16 bit exponents on 32 and 64 bit platform by default. > If only all of of you had read carefully the 543 comments of the update > ticket and remembered this tcomment > https://trac.sagemath.org/ticket/17254#comment:126 and commit > https://git.sagemath.org/sage.git/commit/?id=8c0275427c66b709413188b82da7845a3196e4bb > > that would be obvious to you. > Now if we want to give more bits when fewer variables are used that should > be possible. > (I'm just kidding, this is a not so serious post except for the previous > sentence.) > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
