jsr166 is sort-of an upstream project of openjdk and has its own mailing
list.
It looks like forkjoin changes were discussed here:
https://markmail.org/thread/ezvo7xf3xh6q2u2c
(and yeah, everyone has trouble understanding forkjoin implementation)

On Wed, Feb 27, 2019 at 2:10 PM Chris Dennis <chris.w.den...@gmail.com>
wrote:

> Hi All,
>
> Apologies for dredging up an older mail thread. I lurk and follow along
> with various JDK development threads and this 166 integration change jumped
> out at me. I have to confess although I understood the intent of the change
> and the explanation in the comments, like David I found it very difficult
> to navigate the actual changeset itself. I was hoping that there would be
> continued discussion that I could follow along with and that this would
> help me too.  I was surprised therefore when I didn’t see any further
> discussion, and then noticed that the change had actually been committed (
> http://hg.openjdk.java.net/jdk/jdk/rev/d04f72c354e9). Was there some
> further discussion on another list/thread that I missed that someone could
> direct me to?
>
> Thanks,
>
> Chris
>
> On Feb 10, 2019, at 10:41 PM, David Holmes <david.hol...@oracle.com>
> wrote:
>
>
> 8215363: needless signals in ForkJoinPool
>
> https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/forkjoin-signals/index.html
> https://bugs.openjdk.java.net/browse/JDK-8215363
>
>
> Can't comment - the code is unfathomable.
>
>
>

Reply via email to