If you have used any of the versions of Quantify for UNIX, you will notice that Quantify for Windows is substantially different. The most important differences are listed here:
§ Quantify instruments complete Visual C++ executables, not individual object files at link time.
§ You use the Quantify user interface to perform most operations. (You can also specify Quantify commands in a makefile or from the command line.)
§ You instrument and run a Visual C++ executable in a single step. For more information, click
§ You display the results of each run individually, using a series of data analysis windows: the Call Graph window, the Function List window, the Function Detail window, the Annotated Source window, and the Run Summary window. You can run more than one program at a time and display the results in these windows.
§ You can compare differences between runs directly in Quantify, using the tool button. You don't need to use the qxdiff script.
§ You can use the Navigator to view the run status of programs. For more information, click
§ Quantify uses a pure_api.c file, instead of quantify_stubs.a, to call Quantify API functions from Visual C++ applications. You also add #include "pure.h" to any source file that uses API functions, rather than #include "quantify.h".
§ Quantify saves data in a Quantify data file (.qfy), instead of a .qv file. For more information, click
§ By default, Quantify names and stores instrumented Visual C++ programs in a cache directory, instead of requiring you to name them. However, you can still choose to assign an alternative name to the instrumented program and store it wherever you want. For more information, click
§ Quantify does not use environment variables such as QUANTIFYOPTIONS to control preferences and settings at build time and run time. To change a run-time option, use the Quantify dialog boxes or command-line options.
(C) Copyright IBM Corporation 1993, 2009.