Re: (hypothetical? bogus?) TSAN failure reported in ForkJoinPool (JDK11 and "refresh" versions)
Chris Povirk via Concurrency-interest <[email protected]> Fri, 17 Jul 2020 10:55:06 -0400
| Newsgroups | gmane.comp.java.jsr.166-concurrency |
|---|---|
| Message-ID | <CAEvq2nqPqu-KgB2Q-D-Rp1zqsyMwCoe=z58bk2Uv4vD3gHgamw@mail.gmail.com> |
I built jsr166 from CVS head. I can reproduce the TSAN failure with that. If I edit lockedPush to use setRelease instead of a plain write, the failure goes away. (Oddly, the failure *also* goes away if I merely switch to *setOpaque*, which I would not have thought would be enough. This may well be more of an artifact of what our TSAN can detect. (And again, this whole *failure* may well be an artifact of TSAN.)) _______________________________________________ Concurrency-interest mailing list [email protected] http://cs.oswego.edu/mailman/listinfo/concurrency-interest