Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k
On Thu, 3 Apr 2014, Thorsten Glaser wrote:
> Andreas Schwab dixit:
>
> >Andreas Schwab added the comment:
> >
> >> Enabling this *will* break Python on Linux/m68k
> >
> > ??? It will not of course, it will *fix* it. You have no idea what
> > you are talking about.
>
> No: it will break Debian/m68k which heavily uses Python, because:
>
> - on real metal m68k, the asm function will be tested and work,
> so it will be used, including the new dtoa code
> - the binaries with that will be uploaded to the archive
> - now, on emulated m68k (ARAnyM), those binaries will use the
> new dtoa code instrad of the old one, but the asm instructions
> to change FPU precision will SILENTLY FAIL, which will lead
> to incorrect results
Sorry, what? You seek to veto an upstream Python bug fix because it will
lead to correct binaries that a certain emulator can't handle? That
doesn't make sense (given x86_64 is Turing complete).
Furthermore, Andreas' bug fix was to be merged for python 3.5. Debian is
not obliged to use that version with that patch up until Aranym gets
fixed.
Reply to: