Here are the results using our internal benchmarks which are a mixed a
multi-threaded and single-threaded programs.
This was collected about a month ago but I did not got time to send
due to an unexpected trip.
cmpxchg gives the worst performance due to the memory barriers it incurs.
I'll send a
On Fri, Nov 22, 2013 at 10:49 PM, Rong Xu x...@google.com wrote:
On Fri, Nov 22, 2013 at 4:03 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Fri, Nov 22, 2013 at 4:51 AM, Rong Xu x...@google.com wrote:
Hi,
This patch injects a condition into the instrumented code for edge
counter
On Mon, Nov 25, 2013 at 2:11 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Fri, Nov 22, 2013 at 10:49 PM, Rong Xu x...@google.com wrote:
On Fri, Nov 22, 2013 at 4:03 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Fri, Nov 22, 2013 at 4:51 AM, Rong Xu x...@google.com wrote:
On Fri, Nov 22, 2013 at 4:51 AM, Rong Xu x...@google.com wrote:
Hi,
This patch injects a condition into the instrumented code for edge
counter update. The counter value will not be updated after reaching
value 1.
The feature is under a new parameter --param=coverage-exec_once.
Default is
On Fri, Nov 22, 2013 at 4:03 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Fri, Nov 22, 2013 at 4:51 AM, Rong Xu x...@google.com wrote:
Hi,
This patch injects a condition into the instrumented code for edge
counter update. The counter value will not be updated after reaching
value
Hi,
This patch injects a condition into the instrumented code for edge
counter update. The counter value will not be updated after reaching
value 1.
The feature is under a new parameter --param=coverage-exec_once.
Default is disabled and setting to 1 to enable.
This extra check usually slows
