- 10 3月, 2021 29 次提交
-
-
由 Mikhael Bogdanov 提交于
-
由 Mikhael Bogdanov 提交于
-
由 Andrey Zinovyev 提交于
Fix failing on empty methods inline methods (after light generation) #KT-45032 Fixed
-
由 Dmitry Petrov 提交于
This reverts commit 679756ad
-
由 Vasily Levchenko 提交于
-
由 Vasily Levchenko 提交于
- in kotlin build this is project dependency - in performace build this is artifact dependency
-
由 Vasily Levchenko 提交于
[build][plugin] kotlin native benchmarking plugin adds dependency kotlinx.cli as project dependency
-
由 Vasily Levchenko 提交于
-
由 Vasily Levchenko 提交于
-
由 Vasily Levchenko 提交于
-
由 Sergey Bogolepov 提交于
We need to invoke `llvm-profdata` tool from the same toolchain as Clang (on macOS we use the one from Xcode). (cherry picked from commit 91665b36af68b7fb3a56c0e7ed7ebb7d819adfb2)
-
由 Alexander Shabalin 提交于
(cherry picked from commit af70866594c31c81dfcc41b2e8b33c7a0cdc38f5)
-
由 Sergey Bogolepov 提交于
Provide a `std::system_category` wrapper with the same mangling as in GCC 4.8.5 (cherry picked from commit ec5828a1f375a74a09aa49182571201e1f67b4fa)
-
由 LepilkinaElena 提交于
(cherry picked from commit 8b601d8e2c6bc772386ebd88d303a032a6f54237)
-
由 Igor Chevdar 提交于
Fixes https://youtrack.jetbrains.com/issue/KT-45139 as well (cherry picked from commit 44916e39bfa69325a9ab73cb4533bd2612fb4e56)
-
由 Sergey Bogolepov 提交于
Rebuild linux toolchains with an older OS. (cherry picked from commit 1d249ad7b592573dc4478f0f6cefe2766c323e12)
-
由 Sergey Bogolepov 提交于
Allow toolchain builder to add a suffix to toolchain name. It is useful for rebuilding the same toolchain in different environment. (cherry picked from commit 83148fc5bb4e8bcc5afcf119df53ec1bc854be17)
-
由 Florian Kistner 提交于
* Add ObjC export test with disabled generics * Retain typed generics in ObjC export stubs * Introduce ObjC variance enum to decouple stubs from Kotlin variance (cherry picked from commit 4d7c78b952a467ca3318c8c49d36b768fdc1ef9c)
-
由 LepilkinaElena 提交于
(cherry picked from commit 2f34b0f98e77226f02809a685a96ebb683a69e9d)
-
由 Dmitry Petrov 提交于
-
由 Alexander Udalov 提交于
This will help in diagnosing problems such as KT-45236.
-
由 Alexander Udalov 提交于
Also improve an error message in `IrType.erasedUpperBound`, which seems like a frequent first place where the JVM IR backend crashes in case an error type has made it past psi2ir. This will help in diagnosing problems such as KT-45016.
-
由 Alexander Udalov 提交于
-
由 Alexander Udalov 提交于
Because generateDefaultGetterBody/generateDefaultSetterBody reference the property's backing field, which in case of extension properties leads to an error "Unbound symbols not allowed" because extension property cannot have a backing field. In some way, this check is similar to the `isExpect` check in `generatePrimaryConstructor`.
-
由 Alexander Udalov 提交于
#KT-44496
-
由 Alexander Udalov 提交于
This has no effect on correct code because extension properties cannot have a backing field anyway and that is checked separately. But this function is used in psi2ir to determine whether or not to create a backing field for a property, and in case the code where the property is declared is unreachable like in KT-44496 and has no explicit getter or setter, it would previously return true for extension properties, which on JVM would result in an actual field in the class file, which made no sense. After this change, the compiler will actually crash with an exception in the IR validaton step because the symbol for the field is unbound. That is a bit better than proceeding to generate potentially invalid bytecode, but of course a proper fix would be to report an error in the frontend. #KT-44496
-
由 Ilya Kirillov 提交于
-
由 Ilya Kirillov 提交于
-
由 Pavel Kirpichenkov 提交于
^KT-45145 Fixed
-
- 09 3月, 2021 11 次提交
-
-
由 Ilya Kirillov 提交于
-
由 Pavel Punegov 提交于
-
由 Vladimir Ivanov 提交于
-
由 Jinseong Jeon 提交于
If it's not within a try/catch/finally, that should be an uncaught exception path. ^KT-45327 Fixed
-
由 Jinseong Jeon 提交于
-
由 Alexander Udalov 提交于
Pass parentContext to SamWrapperCodegen from the outside instead of using the one from parentCodegen. The difference is that in case of an inline lambda, we're creating an InlineLambdaContext whose parent is a ClosureContext, but the codegen for that lambda has that latter ClosureContext as its context. So the getNonInlineOuterContext call in SamWrapperCodegen.generateInnerClassInformation wasn't able to identify that this is a context of a lambda that needs to be skipped, and generated it as EnclosingMethod, which caused Java reflection to fail because once that lambda was inlined, it was removed and thus didn't make it to runtime. #KT-44827 Fixed
-
由 Nikolay Krasko 提交于
We have OOM in recent tests executions
-
由 Dmitriy Dolovov 提交于
Also: Rename CirClass.isInline to CirClass.isValue
-
由 Dmitriy Dolovov 提交于
-
由 Dmitriy Dolovov 提交于
-
由 Dmitriy Dolovov 提交于
-