➜

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 Mark.Shannon, neonene, paul.moore, rhettinger, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-09-06.21:52:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630965174.17.0.164145877102.issue45116@roundup.psfhosted.org>
In-reply-to
Content 
> Since PR25244 (28d28e053db6b69d91c2dfd579207cd8ccbc39e7),
_PyEval_EvalFrameDefault() in ceval.c has seemed to be unoptimized with PGO (msvc14.29.16.10).
> At least the functions below have become un-inlined there at all.

I'm not sure if PGO builds are reproducible, since there is a training step which requires to run a non-deterministic workload (the Python test suite which is somehow randomized by I/O timings and other stuffs).

The compiler is free to inline or not depending on the pressure on registers and stack memory. I'm not sure that inlining always make the code faster, since inlining have many side effects.

I don't know well MSC compiler.
History
Date User Action Args
2021-09-06 21:52:54vstinnersetrecipients: + vstinner, rhettinger, paul.moore, tim.golden, Mark.Shannon, zach.ware, steve.dower, neonene
2021-09-06 21:52:54vstinnersetmessageid: <1630965174.17.0.164145877102.issue45116@roundup.psfhosted.org>
2021-09-06 21:52:54vstinnerlinkissue45116 messages
2021-09-06 21:52:54vstinnercreate