RFR 8220238 : Enhancing j.l.Runtime/System::gc specification with an explicit 'no guarantee' statement

[Aleksey Shipilev]

On 5/29/19 5:06 PM, Roger Riggs wrote:
> The language is hard to construct, in part because of the innovations in gc technology that have
> resulted such a wide range of behaviors and timing.
> 
> I'll restore the sentence "When control returns"... but I don't think it carries any
> definite requirement on an implementation. It is benign since 'best effort' is undefined
> and depends on the unspecified intentions of the implementation(s).

"When control returns" does mean things for me (GC implementor). We specifically handle blocking
callers on System.gc() calls in Shenandoah (and partially in Epsilon). I would not be surprised if
JCK has tests for that as well.

I think "best effort" is orthogonal to blocking behavior.

-Aleksey