This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mirabilos
Recipients Arfrever, BreamoreBoy, benjamin.peterson, georg.brandl, larry, loewis, mark.dickinson, mirabilos, pitrou, schwab, skrah, tim.peters
Date 2014-04-03.22:42:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <Pine.BSM.4.64L.1404032239400.28659@herc.mirbsd.org>
In-reply-to <1396563196.41.0.334854177937.issue20904@psf.upfronthosting.co.za>
Content
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

bye,
//mirabilos
-- 
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design.  <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)
History
Date User Action Args
2014-04-03 22:42:18mirabilossetrecipients: + mirabilos, tim.peters, loewis, georg.brandl, mark.dickinson, pitrou, larry, benjamin.peterson, Arfrever, skrah, BreamoreBoy, schwab
2014-04-03 22:42:18mirabiloslinkissue20904 messages
2014-04-03 22:42:18mirabiloscreate