|
From: Xiaoliang L. <xia...@gm...> - 2008-12-02 02:39:32
|
Hi, everyone. Do you know what is the "Instruction Read Accesses (Ir)" event? I really appreciate it if you explain this detailedly or show me where I can learn from. Many thanks for your time. |
|
From: Xiaoliang L. <xia...@gm...> - 2008-12-04 01:40:32
|
Hi, everyone. When using the callgrind, the manual seems to say nothing detailed about the "Instruction Read Accesses (Ir)" event? Do you know what this is? I really appreciate it if you explain this detailedly or show me where I can learn from. Many thanks for your time. |
|
From: Josef W. <Jos...@gm...> - 2008-12-04 09:49:15
|
On Thursday 04 December 2008, Xiaoliang Lee wrote: > Hi, everyone. > > When using the callgrind, the manual seems to say nothing detailed about the > "Instruction Read Accesses (Ir)" event? Do you know what this is? Hmm. It is the same as the Ir event of the Cachegrind tool: "Number of instructions executed". "Ir" is abbreviated for "*R*ead access because of *I*nstruction fetch". A speciality of x86 are instructions with a REP prefix, which can lead to multiple exeuctions of the instruction. Still, "Ir" only counts a 1 here because of the single fetch needed. Josef > I really > appreciate it if you explain this detailedly or show me where I can learn > from. > > Many thanks for your time. > |