Quantify uses debug line information to collect line-by-line performance data. If debug line information is not available for a module, Quantify times that module by default. You can change this default by requesting function level. However, most of the functions, procedures, or methods (collectively referred to here as functions) will be recorded with the name UnnamedFunction and are filtered by default.
For native-compiled (unmanaged) Visual C++ programs, Quantify also requires relocation data to collect data at line or function level. If relocation data is not available for an.exe that was instrumented using inclusive instrumentation, Quantify times the functions. For a DLL, only data for exported functions is recorded. Time for internal, non-exported functions is attributed to the calling exported functions. If you're using Visual Studio 6, you can build a release or debug version of the program that contains relocation data by specifying the /fixed:no and /incremental:no linker options in Visual Studio. For more information on the recommended settings for Visual Studio, click . For those for Visual Studio 6, click
Notes:
§ The Time measurement type is not supported when you are profiling native-compiled code using selective instrumentation.
§ If you choose to time functions in a Visual C++ executable, the only data Quantify includes for the executable is the .exe's entry point. The entry point's function time includes the function time of the other functions in the .exe.
(C) Copyright IBM Corporation 1993, 2009.