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 scoder
Recipients scoder, serhiy.storchaka, vstinner
Date 2016-08-23.17:53:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471974786.13.0.382183237353.issue27841@psf.upfronthosting.co.za>
In-reply-to
Content
If you care so much about C stack space, you could also try to create two or three entry point functions that keep (say) a 4, 8 and 16 items array on the stack respectively, and then pass the pointer (and the overall length if you need it) of that array on into a single function that copies the argument pointers into it and calls the Python function. As long as they are all really simple static functions that end with tail calls (i.e. with "return other_function()"), the C compiler should always be able to inline the entry points into their caller and not waste any additional C stack space for calling them.
History
Date User Action Args
2016-08-23 17:53:06scodersetrecipients: + scoder, vstinner, serhiy.storchaka
2016-08-23 17:53:06scodersetmessageid: <1471974786.13.0.382183237353.issue27841@psf.upfronthosting.co.za>
2016-08-23 17:53:06scoderlinkissue27841 messages
2016-08-23 17:53:06scodercreate