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 Aaron Hall, benjamin.peterson, eric.snow, mark.dickinson, miss-islington, pablogsal, serhiy.storchaka, thatiparthy, vstinner
Date 2018-11-23.12:17:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Unexpected cool effect of static inline functions (copy of my email):

Le jeu. 15 nov. 2018 à 01:06, Gregory P. Smith <greg at> a écrit :
> I expect the largest visible impact may be that a profiler may now attribute CPU cycles takes by these code snippets to the function from the .h file rather than directly to the functions the macro expanded in in the past due to additional debug symbol info attribution. Just more data. Consider that a win.

Oh. That's very interesting.

I just tried gdb and I confirm that gdb understands well inlined
function. When I debug Python, gdb moves into Py_INCREF() or
Py_DECREF() when I use "next".

I also tried perf record/perf report: if I annotate a function
(assembler code of the function), perf shows me the C code of inlined

That's nice!

Date User Action Args
2018-11-23 12:17:33vstinnersetrecipients: + vstinner, mark.dickinson, benjamin.peterson, eric.snow, serhiy.storchaka, thatiparthy, Aaron Hall, pablogsal, miss-islington
2018-11-23 12:17:33vstinnersetmessageid: <>
2018-11-23 12:17:33vstinnerlinkissue35059 messages
2018-11-23 12:17:32vstinnercreate