From f28ba549bbb6bf9e48a06ebd3e2d7b5ed7fa84e6 Mon Sep 17 00:00:00 2001 From: Akihiro Hayashi Date: Tue, 9 Jul 2019 12:44:12 -0400 Subject: [PATCH] Add license information to README.md --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index a694b04..d850a6e 100644 --- a/README.md +++ b/README.md @@ -184,5 +184,8 @@ Again, the code above is pretty much the same as typical CUDA programs. Thanks t Please note that the above example does data transfer optimizations where there is no host-to-device transfer of ```A``` or device-to-host transfer of ```B```. Also, it only allocates and transfers a subarray of ```A``` and ```B``` and invokes the kernel with the subspace since they are safe to do so in this example. However, please be careful about how to optimize your GPU program because the legality of doing so depends on a kernel. For more details, please see the applications in the ```app``` directory. +## License +The GPUIterator module is developed and released under the terms of the Apache 2.0 license. See the LICENSE file in this directory for details. + ## Further Readings "[GPUIterator: Bridging the Gap between Chapel and GPU Platforms](https://cpb-us-e1.wpmucdn.com/blogs.rice.edu/dist/1/2385/files/2019/06/CHIUW19-Chapel-GPUIterator.pdf)", Akihiro Hayashi, Sri Raj Paul, Vivek Sarkar, The ACM SIGPLAN 6th Annual Chapel Implementers and Users Workshop (CHIUW), June 2019. (co-located with PLDI2019/ACM FCRC2019). [slides](https://www.slideshare.net/ahayashi10/gpuiterator-bridging-the-gap-between-chapel-and-gpu-platforms). \ No newline at end of file