➜

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 serhiy.storchaka
Recipients brett.cannon, dino.viehland, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-15.08:40:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481791235.34.0.0480653532145.issue28924@psf.upfronthosting.co.za>
In-reply-to
Content 
Ah, now I see. I was confused by the fact that eval_frame is set only to _PyEval_EvalFrameDefault.

But how large the gain of inlining PyEval_EvalFrameEx()? Is it worth cluttering the code?

Since almost all calls of PyEval_EvalFrameEx() are in the same file as its definition, I suppose the compiler can inline it even without PGO.
History
Date User Action Args
2016-12-15 08:40:35serhiy.storchakasetrecipients: + serhiy.storchaka, brett.cannon, vstinner, dino.viehland, steve.dower
2016-12-15 08:40:35serhiy.storchakasetmessageid: <1481791235.34.0.0480653532145.issue28924@psf.upfronthosting.co.za>
2016-12-15 08:40:35serhiy.storchakalinkissue28924 messages
2016-12-15 08:40:35serhiy.storchakacreate