[issue28006] Remove tracing overhead from the fine-grained fast opcodes

Raymond Hettinger added the comment: I'm going to withdraw this one. I'm not familiar enough with this part of the code to reliably make changes to it. -- status: open -> closed ___ Python tracker ___

[issue28006] Remove tracing overhead from the fine-grained fast opcodes

Raymond Hettinger added the comment: Working on a revised patch. Stand by. -- assignee: steve.dower -> rhettinger ___ Python tracker ___

[issue28006] Remove tracing overhead from the fine-grained fast opcodes

Changes by Raymond Hettinger : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue28006] Remove tracing overhead from the fine-grained fast opcodes

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue28006] Remove tracing overhead from the fine-grained fast opcodes

New submission from Raymond Hettinger: The fast opcodes are ones where we bypass signal/event checking, but they still have the overhead of checking for tracing enabled (this doesn't seem like much, it adds a memory access and can take almost half the time for some of these already quick opcod

[issue28006] Remove tracing overhead from the fine-grained fast opcodes

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python