From aa6d26d41e88634f0c5143bf87154cef1db06dd7 Mon Sep 17 00:00:00 2001 From: "Andrew M. B. Boktor" Date: Wed, 25 Apr 2012 12:16:44 -0800 Subject: Specifying default behaviour of setup_environment Clearer description of how to run [git-p4: depot-paths = "//depot/gpgpu_sim_research/fermi/distribution/": change = 12119] --- README | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README b/README index d12327b..5379932 100644 --- a/README +++ b/README @@ -140,7 +140,8 @@ and run source setup_environment replace with debug or release. Use release if you need faster -simulation and debug if you need to run the simulator in gdb. +simulation and debug if you need to run the simulator in gdb. If nothing is +specified, release will be used by default. Now you are ready to build the simulator, just run @@ -178,11 +179,12 @@ file to "1" (Note: you need CUDA version 4.0 or higher). Now To run a CUDA application on the simulator, simply execute -source setup_environment . +source setup_environment -and just launch the executable as you would if it was to run on the hardware. -To revert back to running on the hardware, remove GPGPU-Sim from your -LD_LIBRARY_PATH environment variable. +Use the same you used while building the simulator. Then just +launch the executable as you would if it was to run on the hardware. To revert +back to running on the hardware, remove GPGPU-Sim from your LD_LIBRARY_PATH +environment variable. Running OpenCL applications is identical to running CUDA applications. However, OpenCL applications need to communicate with the NVIDIA driver in order to -- cgit v1.3