summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAmruth <[email protected]>2018-04-05 16:31:44 -0700
committerAmruth <[email protected]>2018-04-05 16:31:44 -0700
commite1dc8113aa2a51885541f96943bd8d90eaccd968 (patch)
tree846c18633b7b1e656e5986e4a544eca9652a8f89 /README
parent69c57b077d6799f46ad43b99cc0e0049b7c43775 (diff)
fixing file pointer and attributes issues
Diffstat (limited to 'README')
-rw-r--r--README1
1 files changed, 1 insertions, 0 deletions
diff --git a/README b/README
index 4426cdd..543177c 100644
--- a/README
+++ b/README
@@ -349,6 +349,7 @@ process.
** Debugging failing GPGPU-Sim Regressions **
+Credits: Tor M Aamodt
To debug failing GPGPU-Sim regression tests you need to run them locally. The fastest way to do this, assuming you are working with GPGPU-Sim versions more recent than the GPGPU-Sim dev branch circa March 28, 2018 (commit hash 2221d208a745a098a60b0d24c05007e92aaba092), is to install Docker. The instructions below were tested with Docker CE version 18.03 on Ubuntu and Mac OS. Docker will enable you to run the same set of regressions used by GPGPU-Sim when submitting a pull request to https://github.com/gpgpu-sim/gpgpu-sim_distribution and also allow you to log in and launch GPGPU-Sim in gdb so you can inspect failures.