JVM_IR: add $assertionsDisabled when an inlined function uses it
NOTE: jvmCrossinlineLambdaDeclarationSite.kt is muted because the inliner does not remap references to an anonymous object's parent class after regenerating it. Unlike the JVM backend, JVM_IR uses the top level named class' assertion status for all inner classes. (The test used to pass because the lambda in `inline fun call` read the `$assertionsDisabled` field of `CrossinlineLambdaContainer`, which was not reloaded after changing the assertion status of package `test`.)
This commit is contained in:
+1
-2
@@ -1,5 +1,3 @@
|
||||
// IGNORE_BACKEND: JVM_IR
|
||||
// IGNORE_BACKEND_MULTI_MODULE: JVM_IR
|
||||
// FILE: inline.kt
|
||||
// KOTLIN_CONFIGURATION_FLAGS: ASSERTIONS_MODE=jvm
|
||||
// WITH_RUNTIME
|
||||
@@ -28,6 +26,7 @@ class Dummy
|
||||
fun enableAssertions(): CheckerJvmAssertInlineFunctionAssertionsEnabled {
|
||||
val loader = Dummy::class.java.classLoader
|
||||
loader.setClassAssertionStatus("CheckerJvmAssertInlineFunctionAssertionsEnabled", true)
|
||||
loader.setClassAssertionStatus("InlineKt", false)
|
||||
val c = loader.loadClass("CheckerJvmAssertInlineFunctionAssertionsEnabled")
|
||||
return c.newInstance() as CheckerJvmAssertInlineFunctionAssertionsEnabled
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user