Ivan Kylchik
c7435ba760
We are going to deprecate `WITH_RUNTIME` directive. The main reason behind this change is that `WITH_STDLIB` directive better describes its meaning, specifically it will add kotlin stdlib to test's classpath.
47 lines
1.5 KiB
Kotlin
Vendored
47 lines
1.5 KiB
Kotlin
Vendored
// TARGET_BACKEND: JVM_IR
|
|
// WITH_STDLIB
|
|
|
|
// IMPORTANT!
|
|
// Please, when your changes cause failures in bytecodeText tests for 'for' loops,
|
|
// examine the resulting bytecode shape carefully.
|
|
// Range and progression-based loops generated with Kotlin compiler should be
|
|
// as close as possible to Java counter loops ('for (int i = a; i < b; ++i) { ... }').
|
|
// Otherwise it may result in performance regression due to missing HotSpot optimizations.
|
|
// Run Kotlin compiler benchmarks (https://github.com/Kotlin/kotlin-benchmarks)
|
|
// with compiler built from your changes if you are not sure.
|
|
|
|
fun box(): String {
|
|
val uintRange = 1u..7u
|
|
for (i in uintRange step 2) {
|
|
}
|
|
|
|
return "OK"
|
|
}
|
|
|
|
// For "step" progressions in JVM IR, a call to getProgressionLastElement() is made to compute the "last" value.
|
|
// If "step" is called on a non-literal progression, there is a check to see if that progression's step value is < 0.
|
|
// However, if the progression is of type *Range (e.g., IntRange) instead of *Progression (e.g., IntProgression), this
|
|
// check is not needed since *Range always has step == 1.
|
|
//
|
|
|
|
// 0 iterator
|
|
// 0 getStart
|
|
// 0 getEnd
|
|
// 1 getFirst
|
|
// 1 getLast
|
|
// 0 getStep
|
|
// 1 INVOKESTATIC kotlin/internal/UProgressionUtilKt.getProgressionLastElement
|
|
// 0 NEW java/lang/IllegalArgumentException
|
|
// 0 ATHROW
|
|
// 1 INVOKESTATIC kotlin/UnsignedKt.uintCompare
|
|
// 1 IFGT
|
|
// 1 IF_ICMPEQ
|
|
// 2 IF
|
|
// 0 INEG
|
|
// 0 INVOKESTATIC kotlin/UInt.constructor-impl
|
|
// 0 INVOKE\w+ kotlin/UInt.(un)?box-impl
|
|
// 8 ILOAD
|
|
// 5 ISTORE
|
|
// 0 IADD
|
|
// 0 ISUB
|
|
// 1 IINC |