[issue43846] Control stack usage in large expressions

Mark Shannon added the comment: I've not measured performance, as the sort of large literals it would impact are very rare, and the sort of calls it would change are almost non-existent. I'd be surprised if any performance difference could be reliably detected with our current performance to

[issue43846] Control stack usage in large expressions

Change by Mark Shannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue43846] Control stack usage in large expressions

Serhiy Storchaka added the comment: What is performance impact of this change? I expect that creating a list incrementally can hurt performance, but how much? -- nosy: +serhiy.storchaka ___ Python tracker _

[issue43846] Control stack usage in large expressions

Mark Shannon added the comment: New changeset 11e0b295dee235dd6fd66a10d4823b0dcb014dc4 by Mark Shannon in branch 'master': bpo-43846: Use less stack for large literals and calls (GH-25403) https://github.com/python/cpython/commit/11e0b295dee235dd6fd66a10d4823b0dcb014dc4 --

[issue43846] Control stack usage in large expressions

Change by Mark Shannon : -- keywords: +patch pull_requests: +24136 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/25403 ___ Python tracker

[issue43846] Control stack usage in large expressions

Change by Mark Shannon : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue43846] Control stack usage in large expressions

New submission from Mark Shannon : Large literals or function calls with many arguments can consume a lot of stack space. This will be a problem for any future work to use a contiguous stack for data and possibly eliminate frame objects for most calls. It is also possible (I haven't measured