Lines Matching full:specify
109 cost of code at a given position. If you specify multiple cost lines for the
119 ability to specify call relationship among functions. More generally, you
120 specify associations among positions. For this, the second part of the
130 to be able to specify a call to another function in another source file, you
186 needed to specify the same function or same file name multiple times. As
188 to be able to specify integer IDs for position specifications.
192 the format "spec=name", but also "spec=(ID) name" to specify a mapping of an
246 of a program, you specify subposition "instr" in the "positions:" header line,
252 a 16 character long address, one is allowed to specify relative addresses.
256 of the last cost line, and starts with a "+" to specify a positive difference,
257 a "-" to specify a negative difference, or consists of "*" to specify the same
293 can specify a "summary:" line in the header giving the full cost for the
301 abbreviated name. For visualization, it makes sense to be able to specify some
314 to specify an additional event type "Sum", which is calculated by adding costs
483 specify parameters used for the cache simulator. These are the only
499 library file to not have to specify relocation info. For "line",
512 "positions". Callgrind does not add additional cost types. Specify
