New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSR-45 #15684
JSR-45 #15684
Commits on Aug 9, 2022
-
-
-
-
-
-
Solve not registering inlining position for tuples
also removes code that was relocationg inlined calls but now is unreachable
-
-
-
-
-
-
-
Sort inlining requests before creating SMAP
Fixes SMAP generation breaking bytecode idempotency assertions
-
-
Comment out warning about inline positions recording
Such warnings are produced when compiling the bootstrapped compiler.
Commits on Aug 12, 2022
-
Inlined code gets virtual line numbers in stack traces
We follow the Kotlin solution to allow inlined code to point to virtual numbers. We rely on the tooling for proper navigation. See also: https://youtrack.jetbrains.com/issue/KT-8628 https://bugs.openjdk.org/browse/JDK-4972961
-
Fix virtual line numbers in assert-stack
When emitting the bytecode, line numbers are emitted for trees. These line numbers are used in call stack frames. Trees inlined from other files get virtual numbers. It appears that, when inlining `call(x)`, the line number for `call` is emitted before that for `x`. So, if `x` is coming from the current file, its line number will be real and will override that of `call`.