summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorTongzhou Wang <SsnL@users.noreply.github.com>2017-12-01 13:22:46 -0500
committerSoumith Chintala <soumith@gmail.com>2017-12-01 13:22:46 -0500
commitc681b03d374e4010a875018c8a8a0485c40ceb9b (patch)
treef08e0af4e31fa7e524a51e8bacd7cf4016632d1a /CONTRIBUTING.md
parent80c8635a7eaf374b651f479606d0edc651459c39 (diff)
downloadpytorch-c681b03d374e4010a875018c8a8a0485c40ceb9b.tar.gz
pytorch-c681b03d374e4010a875018c8a8a0485c40ceb9b.tar.bz2
pytorch-c681b03d374e4010a875018c8a8a0485c40ceb9b.zip
Add determinant function on variable; Add backward on svd (#3816)
* determinant on variable * svd bwd
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a79fb97f9f..3ad384c20c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -207,7 +207,7 @@ If you are working on the CUDA code, here are some useful CUDA debugging tips:
1. `CUDA_DEBUG=1` will enable CUDA debugging symbols (-g -G). This is particularly
helpful in debugging device code. However, it will slow down the build process,
so use wisely.
-2. `cuda-gdb` and `cuda-memcheck` are your best CUDA debuging friends. Unlike`gdb`,
+2. `cuda-gdb` and `cuda-memcheck` are your best CUDA debugging friends. Unlike`gdb`,
`cuda-gdb` can display actual values in a CUDA tensor (rather than all zeros).