------------------------------------------------------------------------------
NVIDIA Compute Visual Profiler 
MacOS X Release Notes
Version 3.2
------------------------------------------------------------------------------
PLEASE REFER EULA.txt FOR THE LICENSE AGREEMENT FOR USING NVIDIA SOFTWARE.

Please refer Changelog.txt for changes with respect to the previous version.

FILES IN THE RELEASE:
--------------------
* computeprof/computeprof.app    : Compute Visual Profiler executable
                                   For MacOS

* computeprof/doc                : Directory containing files for user documentation.

* computeprof/projects           : Directory containing sample profiler projects


SUPPORTED MACOS X PLATFORMS
---------------------------
Compute Visual Profiler platform support is same as  that for the CUDA Toolkit. 
Please refer the CUDA Toolkit MacOS X release notes.


SYSTEM REQUIREMENTS
-------------------
* CUDA-enabled GPU
  See http://www.nvidia.com/object/cuda_learn_products.html
* NVIDIA Driver
* NVIDIA CUDA Toolkit


INSTALLATION AND SETUP
---------------------
The installation is part of the CUDA toolkit installation. The files are
installed under "<CudaToolkitDir>\computeprof" where <CudaToolkitDir> is the 
directory under which the CUDA Toolkit is installed. 

RUNNING THE Compute Visual Profiler
----------------------------
From Finder run 
   "<CudaToolkitDir>\computeprof\computeprof.app"

From Terminal run
   "<CudaToolkitDir>\computeprof\computeprof.app\Contents\MacOS\computeprof"

Refer the Compute Visual Profiler User Guide "Compute_Visual_Profiler_User_Guide.pdf" for more information.


KNOWN ISSUES
------------
1) Selecting profiler counters can result in an Compute application execution error and profiling 
   data is not generated. In such a case you will not be able to collect any profiling counter data. 
   You can disable all profiler counters and only collect other basic profiling information.

2) Following are some other issues related to profiler counters:
   . "warp serialize" counter for GPUs with compute capability 1.x is known to 
     give incorrect and high values for some cases.

   . "divergent branch" counter for GPUs with compute capability 2.0 is known to
      give an incorrect value zero for some cases.

   . For GPUs with compute capability 2.0 the "instructions issued" and

     "instructions executed" counter values are incorrect for some cases.

3) CUDA driver API trace is not supported


4) Currently there is no way to pass keyboard input to a console-based CUDA
   program which is run from the Compute Visual Profiler. Therefore you must use 
   the command line  argument "--noprompt" to run most of the CUDA SDK 
   samples inside the Compute Visual Profiler.