Hi Andrew,
I just formatted the patch to be same as the other code.
Moreover, I saw the following code in k_standard.c.
if (_LIB_VERSION == _SVID_)
exc.retval = zero;
else
exc.retval = zero/zero;
Do we need to do like that in this patch? It seems to be related to the
old matherr(), but I'
>The only reason why a 0 was observed, was because the cgroup interface
>files were missing and the old code mapped that to a 0. That's no
>longer the case and, thus, it seems it would make the code clearer if
>it wouldn't be there any more.
>
>I don't feel strongly about this, though, and can jus
Hi Matthias,
On Wed, 2020-07-15 at 15:22 +, Baesken, Matthias wrote:
> Hello Severin ,
>
> > the new cgroups implementation
> > supporting v1 and v2 Metrics.getMemoryAndSwapLimit() will never return 0
>
> Wouldn’t it be possible that the coding of getMemoryAndSwapLimit returns
> a
Hi Tagir,
here's yesterday's patch with added unit tests.
Greetings
Raffaello
On 2020-07-29 05:26, Tagir Valeev wrote:
Hello!
Having a unit-test would be nice!
With best regards,
Tagir Valeev.
On Tue, Jul 28, 2020 at 9:04 PM Raffaello Giulietti
wrote:
Hello,
here's a very simple patc
On 20/07/2020 04:51, Ningsheng Jian wrote:
> Since we are getting ready to propose Vector API target to JDK 16 [1]. I
> have regenerated webrev of aarch64 backend parts from panama repo, which
> has been rebased to jdk/jdk very recently, by:
>
> $ hg update vector-unstable && hg diff -r default
