On Fri, 20 May 2022 10:57:44 GMT, Jorn Vernee wrote:
>> This patch is a batch naming cleanup for the foreign linker implementation.
>>
>> The naming changes are as follows:
>>
>> - ProgrammableInvoker -> DowncallLinker
>> - ProgrammableUpcallHandler -> UpcallLinker
>> - 'native invoker' -
- Original Message -
> From: "Tagir Valeev"
> To: "Remi Forax"
> Cc: "core-libs-dev"
> Sent: Monday, May 23, 2022 8:01:44 AM
> Subject: Re: Stream.fromForEach(Consumer>)
> Hello!
>
> There's a Stream.builder for this purpose:
>
> var builder = Stream.builder();
> new Parser("1 2 3").
Hello!
There's a Stream.builder for this purpose:
var builder = Stream.builder();
new Parser("1 2 3").parse(builder);
builder.build().forEach(System.out::println);
A little bit more verbose than your suggestion but this way it's more
clear that the whole stream content will be buffered.
With be
On Wed, 18 May 2022 11:10:58 GMT, Aleksey Shipilev wrote:
> It would be beneficial to bring over the Loom-specific test groups from the
> loom repo to aid development/porting work.
>
> https://github.com/openjdk/loom/blob/fibers/test/jdk/TEST.groups#L97-L108
> https://github.com/openjdk/loom/bl
On Wed, 6 Apr 2022 17:47:53 GMT, Chris Hennick wrote:
> Repeatedly adding DoubleZigguratTables.exponentialX0 to extra causes a
> rounding error to accumulate at the tail of the distribution (probably
> starting around 2*exponentialX0 == 0x1.e46eff20739afp3 ~ 15.1); this fixes
> that by trackin
On Sun, 22 May 2022 16:54:25 GMT, Peter Levart wrote:
> My humble opinion: if java.compiler needs jdk.zipfs for full functionality
Sorry, I wrongly assumed it was `java.compiler` (the library module), but this
is about `jdk.compiler` (the tool)... Nevertheless, the same question applies:
D
On Wed, 18 May 2022 06:30:34 GMT, Adam Sotona wrote:
>> ### Problem description
>> Minimal jdk image created by jlink with the only jdk.compiler module and its
>> dependencies
>> fails to run java source launcher correctly (for example when --source N is
>> specified).
>> Failing source launche
On Sun, 22 May 2022 08:45:48 GMT, Yasumasa Suenaga wrote:
>> I don't think this warning has anything to do with that NULL check. But I'm
>> still not understanding what it is warning about. The "region of size 0" part
>> of the warning message seems important, but I'm not (yet?) seeing how it
>>
On Sun, 22 May 2022 08:35:54 GMT, Yasumasa Suenaga wrote:
>> `Array::_data` is a pseudo flexible array member. "Pseudo" because C++
>> doesn't have flexible array members. The compiler is completely justified in
>> complaining about the apparently out-of-bounds accesses.
>>
>> There is a "well-k
On Sun, 22 May 2022 05:00:21 GMT, Kim Barrett wrote:
>> I guess GCC cannot understand `assert(dest != NULL` immediately preceding it.
>>
>>
>> In file included from
>> /home/ysuenaga/github-forked/jdk/src/hotspot/share/jfr/recorder/checkpoint/types/traceid/jfrTraceIdLoadBarrier.inline.hpp:33,
On Sun, 22 May 2022 03:15:20 GMT, Kim Barrett wrote:
>> Like the others, it is caused by `Array::at_put()`.
>>
>>
>> In file included from
>> /home/ysuenaga/github-forked/jdk/src/hotspot/share/oops/annotations.hpp:28,
>> from
>> /home/ysuenaga/github-forked/jdk/src/hotspot/sh
> I saw some compiler warnings when I tried to build OpenJDK with GCC 12.0.1 on
> Fedora 36.
> As you can see, the warnings spreads several areas. Let me know if I should
> separate them by area.
>
> * -Wstringop-overflow
> * src/hotspot/share/oops/array.hpp
> *
> src/hotspot/share/jfr/
12 matches
Mail list logo
