Please review: 6805748: Assertion "don't reset to 0 -- could be mistaken for never-executed" in CompilationPolicy

[John Rose]

Reviewed; that's a good patch on some bad old code.

Some day soon we'll redo the invocation counters so as to make their  
state transitions much simpler and more coherent with other profiling  
mechanisms.

-- John

On Mar 19, 2009, at 4:30 PM, Coleen Phillimore - Sun Microsystems wrote:

> Summary: Resetting the invocation counter for a method invocation  
> event was setting count to zero for CompileThreshold=1, making it  
> look like a never executed method.