Message267476
I've gotten most tests to past by having FOR_ITER be traced as if the instruction index is that of the corresponding FOR_BEGIN. test_sys_settrace still fails on test_15_loops because an empty loop body doesn't have the 'pass' line traced (ie when FOR_ITER starts the line) which I'm currently pondering ways around
The first patch, which only moved GET_ITER into the closure, would still be good for list/set/dict comprehensions (to help PREDICT & JITs)
If there's essentially a decision that all loops should have JUMP_ABSOLUTE to their beginning for the sake of tracing simplicity, then FOR_BEGIN/FOR_ITER are dead |
|
Date |
User |
Action |
Args |
2016-06-05 20:58:43 | Demur Rumed | set | recipients:
+ Demur Rumed, dino.viehland, serhiy.storchaka |
2016-06-05 20:58:43 | Demur Rumed | set | messageid: <1465160323.12.0.802417528846.issue27127@psf.upfronthosting.co.za> |
2016-06-05 20:58:43 | Demur Rumed | link | issue27127 messages |
2016-06-05 20:58:43 | Demur Rumed | create | |
|