Matthieu Dartiailh

I went ahead with @sweeneyde suggestion and also fixed a bunch of small issues in separate commits (let me know if they should be split into their own PR). I...

I tried to implement stack depth computation on the CFG for the exception table but I do not have it right yet it seems. For the following simple case: ```python...

Sorry for the lack of clarity @iritkatriel My point is that the block starting at offset 40 is the target of 2 exception entry: - the one covering 12 to...

I will try. It is not really a question of interpreting one as two it is just that at the bytecode level I have nothing else than the exception table...

I have a small side question @iritkatriel. According to exception_handling_notes.txt found in cpython repo, exception are pushed as three values. Is this still true ? I am asking because with...

Thanks for your response @iritkatriel I left a small comment on your PR. Also thanks for confirming that I understood correctly what the stack size represent in the exception table....

Thanks for the detailed explanation. It seems I am left with no other option than to reconstruct the setup clause logic from the exception table for the sake of stack...

Yes I meant basic blocks. From the top of my head I do not remember the existence of the equivalent of the COPY/POP_EXCEPT/RERAISE in earlier version bur that may just...

For the simple try/except I have been looking at 3.10 dis gives: ``` 2 0 SETUP_FINALLY 5 (to 12) 3 2 LOAD_CONST 1 (1) 4 STORE_FAST 0 (a) 6 POP_BLOCK...

Going through compile.c I found this line that is slightly surprising to me: https://github.com/python/cpython/blob/3.11/Python/compile.c#L7448 @iritkatriel could explain to me why the block size is adjusted in this way ?