Quantcast
Channel: C#
Viewing all articles
Browse latest Browse all 1853

Symbol Resolution for Intel® Xeon Phi™ Coprocessor Modules

$
0
0

Intel® VTune™ Amplifier resolves symbols for your Intel Xeon Phi coprocessor application on the host during collection post-processing. For proper symbol resolution, you need to specify the search paths to your binary, source and symbol files located on your host system before the collection.

To specify search directories from graphical interface:

  1. Click the Project Properties button on the toolbar and open the Binary/Symbol Search tab for configuring paths for binary or symbol files, or open the Source Search tab for configuring paths for source files.

  2. To add a new search directory in the Search Directories table, click the <Add new search location> row and type the path and name of the directory in the activated text box, or click the ... button on the right to select a directory from the list.

    In almost all cases it is enough to configure a single search directory (top-level project directory) for all types of files. For example, if your project was initially located in C:\work\projects\my_project and then moved to C:\home\mike\my_project_copy, you need to specify the C:\home\mike\my_project_copy as a non-recursive search directory for all file types.

For example, if you use an NFS share to run the application, make sure to specify NFS paths for the application modules and Linux system modules:

To specify search directories from command line:

use the -search-dir option. For example:

amplxe-cl -target-system=mic -collect advanced-hotspots -search-dir C:\mic\nfs -- C:\mic\nfs\matrix\matrix.mic

Re-resolving Results

You can also specify search paths after collection. In this case, you should re-resolve the result to get the symbol information from the binaries once the symbol paths are established.

Inglese

Viewing all articles
Browse latest Browse all 1853

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>