Mads Ager 1f4a3b0d1c [JVM_IR] Avoid safe-call conversions from Byte? and Short? to Int? for ...

comparisons.

Having those conversions leads to unnecesary boxing and null checks.

This change does it only for JVM in the optimization lowering. It
is unclear to me if the other backends can get away with something
similar.

2020-05-08 11:39:30 +03:00

..

byteSmartCast_after.kt

[JVM_IR] Avoid safe-call conversions from Byte? and Short? to Int? for

2020-05-08 11:39:30 +03:00

byteSmartCast_before.kt

[JVM_IR] Avoid safe-call conversions from Byte? and Short? to Int? for

2020-05-08 11:39:30 +03:00

charSmartCast.kt

Return immaterial values from comparison intrinsics

2019-04-10 20:51:46 +02:00

differentTypes_after.kt

JVM: Update tests for IEEE 754 comparisons

2020-01-17 14:14:59 +03:00

differentTypes_before.kt

JVM: Update tests for IEEE 754 comparisons

2020-01-17 14:14:59 +03:00

intSmartCast_after.kt

JVM: Update tests for IEEE 754 comparisons

2020-01-17 14:14:59 +03:00

intSmartCast_before.kt

Update bytecode text tests for JVM_IR

2020-02-18 22:51:29 +03:00

longSmartCast.kt

Return immaterial values from comparison intrinsics

2019-04-10 20:51:46 +02:00

shortSmartCast_after.kt

[JVM_IR] Avoid safe-call conversions from Byte? and Short? to Int? for

2020-05-08 11:39:30 +03:00

shortSmartCast_before.kt

[JVM_IR] Avoid safe-call conversions from Byte? and Short? to Int? for

2020-05-08 11:39:30 +03:00