Integrated: 8278185: Custom JRE cannot find non-ASCII named module inside

2021-12-09 Thread Toshio Nakamura
On Fri, 3 Dec 2021 07:29:17 GMT, Toshio Nakamura wrote: > Could you review this fix? > > Problem: > Custom JRE generated by jlink cannot find non-ASCII named modules included > inside the JRE. > > Cause and fix: > If module or package name was composed by ASCII t

Re: RFR: 8278185: Custom JRE cannot find non-ASCII named module inside

2021-12-07 Thread Toshio Nakamura
On Fri, 3 Dec 2021 07:29:17 GMT, Toshio Nakamura wrote: > Could you review this fix? > > Problem: > Custom JRE generated by jlink cannot find non-ASCII named modules included > inside the JRE. > > Cause and fix: > If module or package name was composed by ASCII t

Re: RFR: 8278185: Custom JRE cannot find non-ASCII named module inside [v2]

2021-12-07 Thread Toshio Nakamura
stringFromByteBufferMatches() miscalculated the length of > matched string. The first part of ASCII characters was missing. This patch > corrected the value. > > Testing: > tier1 and tier2 on Linux have no regression. > I wasn't able to create an automate test for this issue. I apprecia

RFR: 8278185: Custom JRE cannot find non-ASCII named module inside

2021-12-02 Thread Toshio Nakamura
Could you review this fix? Problem: Custom JRE generated by jlink cannot find non-ASCII named modules included inside the JRE. Cause and fix: If module or package name was composed by ASCII then non-ASCII characters, ImageStringsReader:stringFromByteBufferMatches() miscalculated the length of