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 eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2017-03-23.10:22:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490264521.71.0.919134402692.issue29881@psf.upfronthosting.co.za>
In-reply-to
Content
#define _Py_ONCE_VAR(var_decl, var) \
      var_decl var = NULL;
      static _Py_OnceVar var ## _once_meta = {.next = NULL, .obj_ref = (PyObject **) &var}

Yeah, I had a similar idea, but I fear that it will increase the usage of the C stack memory.

See the issue #28858: my old _PyObject_CallArg1() macro allocated an implicit array on the stack and increased the stack usage, whereas the purpose of the macro was to *reduce* the stack usage (just the opposite!). So I removed the macro.
History
Date User Action Args
2017-03-23 10:22:01vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, serhiy.storchaka
2017-03-23 10:22:01vstinnersetmessageid: <1490264521.71.0.919134402692.issue29881@psf.upfronthosting.co.za>
2017-03-23 10:22:01vstinnerlinkissue29881 messages
2017-03-23 10:22:01vstinnercreate