-
Bug
-
Resolution: Unresolved
-
P3
-
11, 17, 25
compiler/stringopts/TestStackedConcatsAppendUncommonTrap.java fails with a wrong result after stacked string concatenation optimizations when run with stress flags.
-Xcomp -XX:CompileThreshold=100 -XX:-TieredCompilation -XX:+DeoptimizeALot
These flags inline 'f' into the main method which is OSR compiled in the failure case (and maybe they avoid the uncommon trap thatJDK-8357105 was caused by).
This bug is hidden byJDK-8273612 since JDK 18, but to my understanding, that fix should not affect correctness, only inlining decisions for the -Xcomp mode.
===
The test runs fine beforeJDK-8271341, then starts crashing until JDK-8291775, and after that it produces the wrong result. The failure mode looks similar to JDK-7179138 since in both cases a result with the wrong length is produced.
-Xcomp -XX:CompileThreshold=100 -XX:-TieredCompilation -XX:+DeoptimizeALot
These flags inline 'f' into the main method which is OSR compiled in the failure case (and maybe they avoid the uncommon trap that
This bug is hidden by
===
The test runs fine before
- caused by
-
JDK-8291775 C2: assert(r != __null && r->is_Region()) failed: this phi must have a region
-
- Resolved
-
- relates to
-
JDK-8271341 Opcode() != Op_If && Opcode() != Op_RangeCheck) || outcnt() == 2 assert failure with Test7179138_1.java
-
- Resolved
-
-
JDK-8273612 Fix for JDK-8272873 causes timeout in running some tests with -Xcomp
-
- Resolved
-
-
JDK-8357105 C2: compilation fails with "assert(false) failed: empty program detected during loop optimization"
-
- Resolved
-
-
JDK-8362118 C2: add more debug prints to string concatenation optimizations
-
- Open
-