Key Features of Tiny-OpenCL Framework
Tiny OpenCL is a lightweight, highly optimized OpenCL implementation designed to compile kernels for execution on the e‑GPU, tailored to resource‑constrained devices.[:cite[1]{ln=1}] The framework translates OpenCL ...
Tiny OpenCL is a lightweight, highly optimized OpenCL implementation designed to compile kernels for execution on the e‑GPU, tailored to resource‑constrained devices.[:cite[1]{ln=1}] The framework translates OpenCL kernels into standard C functions via a parser script, then compiles them with the RISC‑V GNU toolchain and links them with a Tiny‑OpenCL static library to produce the final binary.[:cite[2]{ln=1}] Precompiled software components include a SIMT RISC‑V extension API (for low‑level CU control), startup functions (for per‑thread initialization), and scheduler functions (to assign work‑items across compute resources); these are provided as a static library.[:cite[3]{ln=1}] Scheduling functions read kernel argument fields (global/local sizes) and hardware resource info (compute units, threads, warps) from control/status registers to activate/deactivate resources and distribute work‑items, thereby maximizing parallelism and reducing power use.[:cite[4]{ln=1}] Kernel execution on the e‑GPU proceeds through three phases—startup, scheduling, and processing—with startup initializing threads/warps and stacks before scheduling begins.[:cite[5]{ln=1}] The framework is extended with a lightweight host runtime implementing a subset of the OpenCL runtime API so it can run on Newlib‑based microcontrollers (e.g., X‑HEEP) that lack an OS and multi‑threading support.[:cite[6]{ln=1}] Tiny‑OpenCL’s design and runtime incur measurable scheduling and transfer overheads, but the scheduling delay becomes negligible for sufficiently large problems (matrix sizes 256×256), demonstrating practical overhead/benefit tradeoffs for TinyAI workloads.[:cite[7]{ln=1}][:cite[8]{ln=1}]