238cc7c257
[FIR] Enable BytecodeText tests for FIR.
...
143 out of 767 tests (18.6%) are currently failing.
2020-09-29 10:21:21 +03:00
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
3143b15a17
Generate widening cast for Byte and Short to Int
2020-05-06 14:42:37 +03:00
db17184cfd
[JVM_IR] Avoid some boxing when comparing boxed primitives to primitives.
2020-05-01 13:14:20 +03:00
0b9b1b6945
Update bytecode text tests for JVM_IR
2020-02-18 22:51:29 +03:00
f8341ad7eb
JVM: Update tests for IEEE 754 comparisons
2020-01-17 14:14:59 +03:00
8561f08f06
[JVM_IR] Reintroduce non-IEEE comparisons
...
- Ieee754Equality and PrimitiveComparisons intrinsics
respects absence of -Xproper-ieee754-comparisons, unmuted tests to
show.
2019-11-08 12:58:31 +01:00
31c7183781
Return immaterial values from comparison intrinsics
2019-04-10 20:51:46 +02:00
3a11322506
Enable bytecode text tests for the JVM_IR backend.
2018-12-21 16:20:45 +01:00
8ab7e5c406
KT-10057 Use lcmp instead of Intrinsics.compare
...
Fix of https://youtrack.jetbrains.com/issue/KT-10057
2018-02-14 09:46:29 +01:00
1378b0cf05
Fix bytecode tests after new optimizations
...
- Turn some const conditions into non-const conditions
- Make sure inlined const values are used where required
(otherwise they are eliminated by POP backward propagation)
2017-05-16 17:28:43 +03:00
627dd66ed5
New ieee754 arithmetic, Fix for KT-14651: Floating point comparisons shall operate according to IEEE754
2016-12-09 09:48:46 +01:00
Mark Punzalan