tag:blogger.com,1999:blog-3971202189709462152.post935409618297062344..comments2024-03-11T12:50:02.036+01:00Comments on PyPy Status Blog: Making coverage.py faster under PyPyCarl Friedrich Bolz-Tereickhttp://www.blogger.com/profile/00518922641059511014noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3971202189709462152.post-76512748911600990532013-10-30T08:17:59.686+01:002013-10-30T08:17:59.686+01:00This sounds similar to the -Og setting of GCC, whi...This sounds similar to the -Og setting of GCC, which enables all optimizations which do not interfere with debugging.ArneBabhttps://www.blogger.com/profile/16449390422848764481noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-13545978645222605792013-10-30T08:17:04.784+01:002013-10-30T08:17:04.784+01:00This comment has been removed by the author.ArneBabhttps://www.blogger.com/profile/16449390422848764481noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-7498132839357448902013-10-27T22:09:03.350+01:002013-10-27T22:09:03.350+01:00@Armin: I believe John Doe is talking about the la...@Armin: I believe John Doe is talking about the last paragraph as I believe the JVM also does not disable optimizations when using debug tools.<br /><br />If this is the case than his comment is silly as Alex clearly stated he didn't do an exhaustive search.John M. Camarahttps://www.blogger.com/profile/14679717457363068339noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-80250090208540689642013-10-27T20:37:20.268+01:002013-10-27T20:37:20.268+01:00@John Doe: sadly, we fail to understand exactly wh...@John Doe: sadly, we fail to understand exactly what part of the blog post you're answering to in your sentence "No, you're not the first to make this pretentious mistake". Can you please give more context and elaborate a bit?Armin Rigohttps://www.blogger.com/profile/06300515270104686574noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-26433239080861880882013-10-27T18:53:51.422+01:002013-10-27T18:53:51.422+01:00You misunderstand John Doe. The coverage report i...You misunderstand John Doe. The coverage report is for the user's Python code, which isn't optimized, eliminated, or otherwise modified. The PyPy speedups come from a clever reimplementation of the interpreter that runs the user's Python code, and this article was explaining how they found and fixed a big slowdown that happens to be triggered by a common test-related library.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-75192219662761949322013-10-26T21:40:16.148+02:002013-10-26T21:40:16.148+02:00No, you're not the first to make this pretenti...No, you're not the first to make this pretentious mistake.<br /><br />What's the report for code that was actually eliminated by optimizations? Was it covered? Was it not?John Doenoreply@blogger.com