Stack size miscalculated with try-catch blocks

[Rafael Winterhalter]

Is this pushed to master? I still experience these errors on multiple test
cases.

Am Mi., 30. Okt. 2024 um 10:19 Uhr schrieb Adam Sotona <
adam.sotona at oracle.com>:

> Hi Rafael,
>
> Please update to the latest codebase, maxstack of the provided test case
> is correctly calculated now.
>
>
>
> Thanks,
>
> Adam
>
>
>
>
>
> *From: *classfile-api-dev <classfile-api-dev-retn at openjdk.org> on behalf
> of Rafael Winterhalter <rafael.wth at gmail.com>
> *Date: *Thursday, 24 October 2024 at 8:33
> *To: *classfile-api-dev <classfile-api-dev at openjdk.org>
> *Subject: *Stack size miscalculated with try-catch blocks
>
> Hello,
>
>
>
> when testing a recent build of the JDK with my bridge to ASM, I
> encountered some test failures. This is related to the stack size of a
> method being calculated with an additional, unnecessary slot. This can be
> reproduced using https://github.com/raphw/asm-jdk-bridge
>
>
>
> This can also be reproduced by inspecting the computed stack for:
>
> void c() {
>     try {
>         throw new RuntimeException();
>     } catch (RuntimeException e) {
>     }
> }
>
> which will be computed as 3 and not 2.
>
>
>
> Best regards, Rafael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/classfile-api-dev/attachments/20241030/de2b8b5f/attachment-0001.htm>