JDK-8143900 : OptimizeStringConcat has an opaque dependency on Integer.sizeTable field
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9,10
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-11-24
  • Updated: 2018-10-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8136500 - Integer/Long getChars and stringSize should be more idiomatic
Relates :  
JDK-8143859 - branch nests testing for intervals should be converted to internal switch ranges and rebalanced
Description
During the work on JDK-8136500, it was discovered that OptimizeStringConcat code in C2 has its own Integer.stringSize copy, which references Integer.sizeTable static field. Removing that static field silently breaks OptimizeStringConcat, making it to bail every time. (There is an assert that fails in fastdebug build).

After JDK-8136500 is done, we need to figure out the way to remove Integer.sizeTable and/or rewrite the PhaseStringOpts::int_stringSize to match JDK-8136500 changes.
Comments
It's not clear if it makes sense to spend time on this after Indify String Concatenation JDK-8085796 was completed.
14-02-2017