On Mon, 21 Feb 2022 18:05:08 GMT, Lance Andersen wrote:
>>> The change looks innocuous so it is probably OK. I would like to kick of
>>> our Mach5 runs to see if it shakes out any potential issues.
>>
>> @LanceAndersen , did you manage to get any Mach5 results? Did you find any
>> issues?
>
>>
On Thu, 17 Feb 2022 16:02:42 GMT, Volker Simonis wrote:
>> Currently, `InflaterInputStream::read()` first does a native call to the
>> underlying zlib `inflate()` function and only afterwards checks if the
>> inflater requires input (i.e. `Inflater::needsInput()`) or has finished
>> inflating
On Mon, 21 Feb 2022 18:05:08 GMT, Lance Andersen wrote:
> > > The change looks innocuous so it is probably OK. I would like to kick of
> > > our Mach5 runs to see if it shakes out any potential issues.
> >
> >
> > @LanceAndersen , did you manage to get any Mach5 results? Did you find any
> >
On Mon, 21 Feb 2022 10:06:40 GMT, Volker Simonis wrote:
> > The change looks innocuous so it is probably OK. I would like to kick of
> > our Mach5 runs to see if it shakes out any potential issues.
>
> @LanceAndersen , did you manage to get any Mach5 results? Did you find any
> issues?
Tests
On Thu, 17 Feb 2022 16:02:42 GMT, Volker Simonis wrote:
>> Currently, `InflaterInputStream::read()` first does a native call to the
>> underlying zlib `inflate()` function and only afterwards checks if the
>> inflater requires input (i.e. `Inflater::needsInput()`) or has finished
>> inflating
On Thu, 17 Feb 2022 16:02:42 GMT, Volker Simonis wrote:
>> Currently, `InflaterInputStream::read()` first does a native call to the
>> underlying zlib `inflate()` function and only afterwards checks if the
>> inflater requires input (i.e. `Inflater::needsInput()`) or has finished
>> inflating
On Fri, 18 Feb 2022 08:46:51 GMT, Volker Simonis wrote:
> The change looks innocuous so it is probably OK. I would like to kick of our
> Mach5 runs to see if it shakes out any potential issues.
@LanceAndersen , did you manage to get any Mach5 results? Did you find any
issues?
-
P
On Thu, 17 Feb 2022 20:58:54 GMT, Lance Andersen wrote:
> The change looks innocuous so it is probably OK. I would like to kick of our
> Mach5 runs to see if it shakes out any potential issues.
>
Thanks Lance! Much appreciated.
> From reading the 3rd party problem reports, it appears that the
On Thu, 17 Feb 2022 16:02:42 GMT, Volker Simonis wrote:
>> Currently, `InflaterInputStream::read()` first does a native call to the
>> underlying zlib `inflate()` function and only afterwards checks if the
>> inflater requires input (i.e. `Inflater::needsInput()`) or has finished
>> inflating
On Thu, 17 Feb 2022 10:01:11 GMT, Claes Redestad wrote:
>> Volker Simonis has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Changed hardcoded constant to JMH parmater and removed non-ASCII chars
>> from comments
>
> test/micro/org/openjdk
> Currently, `InflaterInputStream::read()` first does a native call to the
> underlying zlib `inflate()` function and only afterwards checks if the
> inflater requires input (i.e. `Inflater::needsInput()`) or has finished
> inflating (`Inflater::finished()`). This leads to an unnecessary native
On Thu, 17 Feb 2022 09:35:47 GMT, Christoph Langer wrote:
> Makes sense to me. Benchmark numbers look good.
Thanks Christoph!
-
PR: https://git.openjdk.java.net/jdk/pull/7492
12 matches
Mail list logo
