Am 31.08.2015 um 17:10 schrieb Florian Krohm:
> On 28.08.2015 09:03, Josef Weidendorfer wrote:
>
>> This suggests we should document the difference between
>> START/STOP_INSTRUMENTAITON
>> and TOGGLE_COLLECT better.
>
> Hmm, yes :) Any chance you can write something up in time for 3.11 ?
This i
On 28.08.2015 09:03, Josef Weidendorfer wrote:
> This suggests we should document the difference between
> START/STOP_INSTRUMENTAITON
> and TOGGLE_COLLECT better.
Hmm, yes :) Any chance you can write something up in time for 3.11 ?
>
>> for (int i = 1; i <= 1000; ++i) {
>>CALLGRIN
Am 27.08.2015 um 22:53 schrieb Philippe Waroquiers:
> E.g. I think that stop instrumentation implies to flush the translation
> cache. But the currently executed block will not be really flushed till
> the block is exited.
To my understanding, every client request forces a block to end. It is fine
Hi Geoff,
Am 27.08.2015 um 08:42 schrieb galexand...@nc.rr.com:
> I would like to count instructions for a specific part of my code.
> ...
This suggests we should document the difference between
START/STOP_INSTRUMENTAITON
and TOGGLE_COLLECT better. Anyway.
> for (int i = 1; i <= 1000; ++i)
I tried the below (the toggle version, translated to c) on x86,
with gcc 4.9.2.
Looking at the printf call, I see:
0x080483e2 <+178>: push $0x7a314
0x080483e7 <+183>: push $0x80485d0
0x080483ec <+188>: call 0x80482f0
So, you see that 0x7a314 (so 500500 in decimal) is pushed.
I would like to count instructions for a specific part of my code.
I found a valgrind-users thread, "A great trick for counting cycles using
callgrind - but what about massif?"
(http://sourceforge.net/p/valgrind/mailman/message/33476105/), that gives a way
to use Callgrind to do this using the
