On Wed, 3 Jun 2026 13:43:03 GMT, Jaikiran Pai <[email protected]> wrote:
>>> @jaikiran, is my understanding correct that by "reintroduce the change that >>> was done for JDK-7036144" you implicitly also mean to reintroduce the fix >>> [JDK-8374644](https://bugs.openjdk.org/browse/JDK-8374644) for the >>> performance regression >> >> Correct. > >> Expand the test coverage. It's always risky to change something in code from >> JDK 1.0/1.1 so having tests that capture the current behavior (even if >> unspecified) is important before making any change. > > A new test has been proposed https://bugs.openjdk.org/browse/JDK-8385891 to > help increase the coverage. Over time, more will be added. > Jai, Lance and I met today to go over the issues with GZIPInputStream. Here's > a summary of where we got to: > > For JDK 28 or later, introduce a new constructor to create a > GZIPInputStream that works like it should have done in JDK 1.1 when the API > was originally introduced. We discussed two possible sets of parameters. We > also discussed maybe deprecating the two existing constructors due to the > issue of treating available==0 as EOF and the issue of swallowing exceptions. I've filed https://bugs.openjdk.org/browse/JDK-8388919 to track this. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30925#discussion_r3643464958
