Importing legacy data files to the VTune™ Amplifier XE

The VTune™ Amplifier XE is designed so that profiling results collected on Linux system could be opened on Windows system, and vice versa. However, in some cases the results collected with the older versions of VTune Amplifier XE cannot be opened in GUI directly due to backward incompatibility of project data structure. For example, opening the Lightweight Hotspots results collected with the Beta version of the VTune™ Amplifier XE may result in the following error message:

Open+result+error.jpg

When opening Event-based Sampling analysis results, you can try to overcome the legacy data structure incompatibility problem by using the command line option to import the raw collection data.

The -import option creates a result directory by importing one or more legacy data files/directories.

For example:

>amplxe-cl.exe -result-dir=r000 -import=C:\My_Old_Project\sample1234.tb5 -search-dir=C:\My_Old_Project\bin

In this example, you specify a result directory name for saving new results data and set the path to the legacy data files or directories.

It is highly recommended to point out the path to the application binaries using the -search-dir option for addresses resolution. For more details on the -search-dir option, use the amplxe-cl.exe -help command.

Note: the import functionality is designed to handle specifically the event-based sampling collection raw data, namely .tb* files. So, you can import the .tb5 files collected with the VTune™ Performance Analyzer 9.x or .tb6 files collected with the older versions of the VTune Amplifier XE. This functionality is not intended to work with legacy results collected with Hotspot Analysis, Concurrency Analysis, Locks and Waits analysis of previous versions of the VTune™ Amplifier XE. If you face a problem of opening such results, submit a support request at http://premier.intel.com for investigation.

 

 

Pour de plus amples informations sur les optimisations de compilation, consultez notre Avertissement concernant les optimisations.