[JVM_IR] Fix line number information for try-catch.

In particular, the current line numbers could lead to stepping
into the catch handler even when the code in the try did not
throw an exception.

This was caused by the code materializing the final value having
the catch line number. This patch delays the materialization
until the line number of the usage has been emitted.
This commit is contained in:
Mads Ager
2020-05-28 13:04:59 +02:00
committed by max-kammerer
parent 5efbe6ae15
commit f128e5222a
4 changed files with 77 additions and 33 deletions
+6 -3
View File
@@ -34,9 +34,10 @@ fun box() {
foo()
}
// IGNORE_BACKEND: JVM_IR
// The JVM_IR backend goes back to line 13 after line 14. It has the
// sequence 13, 14, 13 which doesn't make sense.
// The JVM backend steps back to line 11 when leaving the
// `mightThrow2` call. The JVM_IR backend does not. The
// JVM_IR behavior is consistent with what happens for the
// try-finally where the value is discarded which seems good.
// LINENUMBERS
// test.kt:29 box
@@ -50,7 +51,9 @@ fun box() {
// test.kt:11 foo
// test.kt:25 mightThrow2
// test.kt:26 mightThrow2
// LINENUMBERS JVM
// test.kt:11 foo
// LINENUMBERS
// test.kt:13 foo
// test.kt:14 foo
// test.kt:10 foo