RFR(T): 8214857: "bad trailing membar" assert failure at memnode.cpp:3220
tobias.hartmann at oracle.com
Wed Dec 5 12:48:10 UTC 2018
looks good to me too. How did you reproduce this?
On 05.12.18 11:58, Roland Westrelin wrote:
> When going from a trailing membar to the corresponding leading membar,
> if a dead end is hit (top/null control input), the logic must go back to
> the last region it encountered and try its next input. Currently the
> code pops all regions it encountered.
> I consider this change trivial and will push it with a single review.
More information about the hotspot-compiler-dev