➜

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 vstinner
Recipients josh.r, rhettinger, serhiy.storchaka, sir-sigurd, vstinner
Date 2019-02-26.22:35:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551220525.53.0.316770475269.issue36030@roundup.psfhosted.org>
In-reply-to
Content 
> if LTO is enabled, the same stack bloat issues are possible

Please test, I'm not interested to spend too much time on that topic.

To be clear, _Py_NO_INLINE was a hack and a micro-optimization. It doesn't solve a real bug. Python has very weak promises on the maximum stack depth.

My work on reducing the stack memory usage was mostly motivated by my work on FASTCALL, since some patches reduced the maximum stack depth. They increased the stack memory usage with micro-optimizations like "PyObject *small_stack[_PY_FASTCALL_SMALL_STACK];" which is allocated on ths stack: see Objects/call.c.
History
Date User Action Args
2019-02-26 22:35:25vstinnersetrecipients: + vstinner, rhettinger, serhiy.storchaka, josh.r, sir-sigurd
2019-02-26 22:35:25vstinnersetmessageid: <1551220525.53.0.316770475269.issue36030@roundup.psfhosted.org>
2019-02-26 22:35:25vstinnerlinkissue36030 messages
2019-02-26 22:35:25vstinnercreate