opencl
Here are 1,023 public repositories matching this topic...
-
Updated
Sep 20, 2021 - Python
-
Updated
Sep 16, 2021 - C++
how to use gui in the AidLearning?how to custom the gui?
Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.
This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.
As of 00e1f52cf95c16b0cea34c83372145532b4745ba the LWJGL codebase has a new directory layout. This has broken the included Eclipse project.
Assimp Tutorial
-
Updated
Sep 17, 2021 - C++
-
Updated
Sep 13, 2021 - C#
-
Updated
Aug 26, 2021 - C++
-
Updated
Sep 11, 2018 - C++
In order to test manually altered IR, it would be nice to have a --skip-compilation flag for futhark test, just like we do for futhark bench.
-
Updated
Aug 19, 2021 - C++
BuildTools-generated Pfn* structures implement IDisposable so that SilkMarshal.Free can be called to unpin the delegate and allow the GC to have at it. The Vulkan Pfn* structures, which are manually written, do not implement this at the moment and cause (very minor) memory leaks.
The work is:
- look at how the Pfn* structures in one of the other libraries (for example SDL) does it
- make
-
Updated
Sep 12, 2021 - Clojure
-
Updated
Sep 8, 2021 - Nim
-
Updated
Mar 23, 2021 - C
-
Updated
Aug 16, 2021 - Python
-
Updated
Sep 11, 2021 - Rust
-
Updated
Sep 19, 2021 - C++
-
Updated
Jul 18, 2021 - C++
-
Updated
Jul 9, 2021 - C++
-
Updated
Jul 26, 2021 - Python
-
Updated
Aug 27, 2021 - C++
Improve this page
Add a description, image, and links to the opencl topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the opencl topic, visit your repo's landing page and select "manage topics."
Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)