JVM: erase conditional suspension markers from inline-only functions

Otherwise, the generated bytecode is unnecessarily suboptimal in some
(arguably weird) cases.

In the JVM backend, this was an accidental regression in #3260, as I had
not noticed that effectively inline-only functions were handled by a
separate branch in FunctionCodegen. In JVM_IR, I'm pretty sure the
redundant markers have always been there as `isSuspensionPoint` in
ExpressionCodegen never checked for effectively-inline-only-ness.

This commit is contained in:

pyos

2020-04-07 18:08:33 +02:00

committed by

Ilmir Usmanov

parent f6d9867fa4

commit 0037d5a7c8

6 changed files with 34 additions and 14 deletions

									
										compiler/testData/codegen/bytecodeText/coroutines/effectivelyInlineOnly.kt
									
Vendored

		+4
		
												View File
												
				@@ -0,0 +1,4 @@

				// WITH_COROUTINES

				// TREAT_AS_ONE_FILE

				inline suspend fun <reified T> f(x: suspend () -> T) = x()

				// 0 InlineMarker