New submission from Mark Shannon <m...@hotpy.org>:
Computing whether an instruction is the first on a line (for tracing) in the interpreter is complicated and slow. Doing it in the compiler should be simpler and has no runtime cost. Currently we decide if the current instruction is the first on a line, by using the `co_lines` table, but if the previous instruction executed was a jump from the same line over a block of instructions with different line number(s) then we can get this wrong. This doesn't seem to a problem now, but could be with either: Specialization of FOR_ITER inlining generators, or Compiler improvements leading to different code layout. The table is only one bit per instruction, so shouldn't be a problem in terms of space. ---------- components: Interpreter Core messages: 413651 nosy: Mark.Shannon, iritkatriel priority: normal severity: normal status: open title: Add a line-start table to the code object. type: behavior versions: Python 3.11 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46817> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
