Lines Matching refs:profiling

38 * Introduction::        What profiling means, and why it is useful.
40 * Compiling:: How to compile your program for profiling.
49 * Details:: Details of how profiling is done
75 * You must compile and link your program with profiling enabled.
103 To better understand how profiling works, you may wish to read a
114 compile and link it with profiling enabled.
116 To compile a source file for profiling, specify the '-pg' option when
120 To link the program for profiling, if you use a compiler such as 'cc'
123 to do what is necessary for profiling. Here are examples:
153 such as 'cc', you may have to specify a profiling startup file 'gcrt0.o'
155 addition, you would probably want to specify the profiling C library,
164 libraries you may run into problems with the profiling support code in a
168 against a static version of the library containing the profiling support
183 If you wish to perform line-by-line profiling you should use the
187 Note, older versions of 'gcc' produce line-by-line profiling
195 their program. This can be used to implement an alternative profiling
204 Once the program is compiled for profiling, you must run it in order to
237 Older versions of the GNU profiling library may also write a file
408 suggested function ordering for the program based on profiling
420 link line ordering for the program based on profiling data. This
496 compiled with profiling enabled are also identified, but only if
515 The '-l' option enables line-by-line profiling, which causes
523 executed. While line-by-line profiling can help isolate where in a
554 useful for profiling kernel modules.
730 not mentioned. Note that if a function was not compiled for profiling,
759 functions 'mcount' and 'profil' are part of the profiling apparatus and
761 of overhead due to profiling.
806 compiled with profiling enabled), the "calls" field is blank.
880 The internal profiling function 'mcount' (*note The Flat Profile:
1203 profiling. In this mode, histogram samples are assigned not to
1207 line-by-line profiling information.
1222 profiling. Note that 'ct_init' accounted for four histogram hits, and
1248 this time with line-by-line profiling enabled. Note that 'ct_init''s
1416 _on the average_ from one profiling run to the next. (_Sometimes_ it
1563 * Implementation:: How a program collects profiling information
1583 The 'mcount' routine, included in the profiling library, is
1606 profiling version of the library.
1632 overhead than kernel-based profiling. Also, due to the added delay
1638 special profiling startup file 'gcrt0.o', which invokes 'monstartup'
1655 The profiling library also includes a function ('mcleanup') which is
1710 this does not include the size of the header), the rate of the profiling
1712 being scaled by the profiling clock rate. The physical dimension is
1722 not a physical dimension). Also, the profiling rate would have to be
1738 callee's function. When performing profiling at the function level,
1740 However, when profiling at the line-level, it is better if the addresses
1774 lists EXCL_TIME and EXCL_GRAPH, and if line-by-line profiling is
1787 whether line-by-line profiling ('-l' option) has been enabled. For
1788 normal profiling, the BFD canonical symbol table is scanned. For
1789 line-by-line profiling, every text space address is examined, and a new
1844 if line-by-line profiling has been selected. Each basic-block address
1860 to the degree of overlap. This effect is rare for normal profiling, but
1861 overlaps are more common during line-by-line profiling, and can cause
1927 file. For line-by-line profiling ('-l' option), also shows line