RFR(L): JDK-8046936 : JEP 270: Reserved Stack Areas for Critical Sections
dl at cs.oswego.edu
Mon Nov 23 00:04:51 UTC 2015
On 11/20/2015 12:40 PM, Karen Kinnear wrote:
> Totally appreciate the suggestion that the java.util.concurrent modifications
> be done by folks with more domain expertise.
> Would you have us incorporate the initial minimal set of j.u.c. updates or none
> at all?
Sorry that I'm still in foot-drag mode on this.
Reading David and Fred's exchanges reinforce my thoughts
that there is no defensible rule or approach to
use @ReservedStackAccess so as to add as little time and
space as possible to reduce the occurrence of stuck
resources as much as possible during StackOverflowError.
After googling "StackOverflowError java util concurrent" and seeing the
range of situations that can be encountered, I don't even know
which kinds of constructions to target.
And I'm less sure whether using @ReservedStackAccess at all
is better than doing nothing.
Maybe there is some decent empirical strategy, but I can't
tell until hotspot support of @ReservedStackAccess is in place.
So my vote is still to keep the JDK changes out for now.
More information about the core-libs-dev