delta/cpython-git.git/Python/peephole.c, branch misc-acks-comment github.com: python/cpython.git Produce cleaner bytecode for 'with' and 'async with' by generating separate code for normal and exceptional paths. (#6641) 2019-11-21T09:11:43+00:00 Mark Shannon mark@hotpy.org 2019-11-21T09:11:43+00:00 fee552669f21ca294f57fe0df826945edc779090 Remove BEGIN_FINALLY, END_FINALLY, CALL_FINALLY and POP_FINALLY bytecodes. Implement finally blocks by code duplication. Reimplement frame.lineno setter using line numbers rather than bytecode offsets. 
Remove BEGIN_FINALLY, END_FINALLY, CALL_FINALLY and POP_FINALLY bytecodes. Implement finally blocks by code duplication.
Reimplement frame.lineno setter using line numbers rather than bytecode offsets.
 Fix unused variable and signed/unsigned warnings (GH-15537) 2019-08-27T16:55:13+00:00 Raymond Hettinger rhettinger@users.noreply.github.com 2019-08-27T16:55:13+00:00 0138c4ceab1e10d42d0aa962d2ae079b46da7671 






bpo-37289: Remove 'if False' handling in the peephole optimizer (GH-14099)
2019-06-15T14:58:00+00:00

Pablo Galindo
Pablogsal@gmail.com

2019-06-15T14:58:00+00:00

7a68f8c28bb78d957555a5001dac4df6345434a0















bpo-37269: Correctly optimise conditionals with constant booleans (GH-14071)
2019-06-14T05:54:53+00:00

Pablo Galindo
Pablogsal@gmail.com

2019-06-14T05:54:53+00:00

05f831865545b08c9a21cfb7773af58b76ec64cb

Fix a regression introduced by af8646c8054d0f4180a2013383039b6a472f9698 that was causing code of the form:

if True and False:
   do_something()

to be optimized incorrectly, eliminating the block.




Fix a regression introduced by af8646c8054d0f4180a2013383039b6a472f9698 that was causing code of the form:

if True and False:
   do_something()

to be optimized incorrectly, eliminating the block.






bpo-37213: Handle negative line deltas correctly in the peephole optimizer (GH-13969)
2019-06-13T18:16:22+00:00

Pablo Galindo
Pablogsal@gmail.com

2019-06-13T18:16:22+00:00

3498c642f4e83f3d8e2214654c0fa8e0d51cebe5

The peephole optimizer was not optimizing correctly bytecode after negative deltas were introduced. This is due to the fact that some special values (255) were being searched for in both instruction pointer delta and line number deltas.




The peephole optimizer was not optimizing correctly bytecode after negative deltas were introduced. This is due to the fact that some special values (255) were being searched for in both instruction pointer delta and line number deltas.






bpo-1875: Raise SyntaxError in invalid blocks that will be optimised away (GH-13332)
2019-05-17T10:37:08+00:00

Pablo Galindo
Pablogsal@gmail.com

2019-05-17T10:37:08+00:00

af8646c8054d0f4180a2013383039b6a472f9698

Move the check for dead conditionals (if 0) to the peephole optimizer
and make sure that the code block is still compiled to report any
existing syntax errors within.




Move the check for dead conditionals (if 0) to the peephole optimizer
and make sure that the code block is still compiled to report any
existing syntax errors within.






bpo-9566: Fix compiler warnings in peephole.c (GH-10652)
2018-12-07T16:54:18+00:00

Victor Stinner
vstinner@redhat.com

2018-12-07T16:54:18+00:00

028f0ef4f3111d2b3fc5b971642e337ba7990873












bpo-35193: Fix an off by one error in the RETURN_VALUE case. (GH-10418)
2018-11-09T01:55:07+00:00

Gregory P. Smith
greg@krypto.org

2018-11-09T01:55:07+00:00

49fa4a9f1ef387e16596f271414c855339eadf09

Fix an off by one error in the peephole optimizer when checking for unreachable code beyond a return.

Do a bounds check within find_op so it can return before going past the end as a safety measure.

https://github.com/python/cpython/commit/7db3c488335168993689ddae5914a28e16188447#diff-a33329ae6ae0bb295d742f0caf93c137
introduced this off by one error while fixing another one nearby.

This bug was shipped in all Python 3.6 and 3.7 releases.

The included unittest won't fail unless you do a clang msan build.




Fix an off by one error in the peephole optimizer when checking for unreachable code beyond a return.

Do a bounds check within find_op so it can return before going past the end as a safety measure.

https://github.com/python/cpython/commit/7db3c488335168993689ddae5914a28e16188447#diff-a33329ae6ae0bb295d742f0caf93c137
introduced this off by one error while fixing another one nearby.

This bug was shipped in all Python 3.6 and 3.7 releases.

The included unittest won't fail unless you do a clang msan build.






bpo-17611. Move unwinding of stack for "pseudo exceptions" from interpreter to compiler. (GH-5006)
2018-02-22T21:33:30+00:00

Serhiy Storchaka
storchaka@gmail.com

2018-02-22T21:33:30+00:00

520b7ae27e39d1c77ea74ccd1b184d7cb43f9dcb



Co-authored-by: Mark Shannon <mark@hotpy.org>
Co-authored-by: Antoine Pitrou <antoine@python.org>







Co-authored-by: Mark Shannon <mark@hotpy.org>
Co-authored-by: Antoine Pitrou <antoine@python.org>







bpo-29469: peephole: Remove const_stack (GH-4879)
2017-12-18T06:52:54+00:00

INADA Naoki
methane@users.noreply.github.com

2017-12-18T06:52:54+00:00

87010e85cb37192d63b1a30e5fabba307ad5a3f5

Constant folding was moved to AST optimizer.
But compiler may emit LOAD_CONSTs + BUILD_TUPLE.
For example, default arguments can be constant tuple
if all arguments are constant.

This commit makes peephole's tuple folding simple.
It doesn't support nested tuples because nested
tuples are folded by AST optimizer already.




Constant folding was moved to AST optimizer.
But compiler may emit LOAD_CONSTs + BUILD_TUPLE.
For example, default arguments can be constant tuple
if all arguments are constant.

This commit makes peephole's tuple folding simple.
It doesn't support nested tuples because nested
tuples are folded by AST optimizer already.