CUDA Float32 Buffers #
Low-level buffer operations for the native CUDA autograd runtime. CUDA builds use
csrc/cuda/tensor/torchlean_cuda_tensor.cu; ordinary CPU builds link the parity implementation in
csrc/cuda/tensor/torchlean_cuda_tensor_stub.c so that the same runtime interfaces remain testable.
Runtime Availability #
What implementation sits behind the CUDA FFI symbols in the current process.
- cpuStub : RuntimeStatus
Default non-CUDA builds provide host-memory parity stubs for low-level tests.
- nativeAvailable : RuntimeStatus
The project was built with CUDA and at least one CUDA device is visible.
Instances For
Instances For
Query whether the linked CUDA symbols are native or the CPU parity stubs.
Instances For
Require real CUDA execution for a user-selected CUDA session.
Instances For
Deterministic Reductions Mode #
TorchLean's CUDA runtime uses atomicAdd in a few kernels to accumulate float32 results. This is
fast, but floating-point addition is non-associative, and CUDA does not fix a global order for the
interleaving of atomic updates. As a result, some kernels can be bit-nondeterministic across runs.
TorchLean therefore exposes an opt-in deterministic mode that replaces those atomic accumulation paths with fixed-order reductions. This trades performance for reproducibility.
This flag is a runtime setting affecting only the CUDA/stub backends; it has no effect on the pure Lean Spec.
Enable/disable deterministic reductions mode and return the observed flag value.
Why this helper exists: the raw setter returns Unit, so if you write let _ := set... in
Lean, the compiler is free (under pure semantics) to reorder or eliminate that call. The runtime
therefore provides a *_checked wrapper that both sets the flag and returns the observed value,
giving us a single call with an explicit return value dependency.
Instances For
Enable/disable deterministic reductions mode (see module docstring).
Instances For
Query whether deterministic reductions mode is enabled.
Instances For
Allocator Telemetry #
Snapshot of the CUDA buffer allocator.
liveBytes/peakBytes count device or stub payloads allocated by this runtime layer. The wrapper
counters track the Lean external objects that own those payloads; in a steady workload,
wrapperAllocCount - wrapperFinalizeCount should remain bounded. deviceFreeBytes and
deviceTotalBytes come from cudaMemGetInfo in the CUDA build and are 0 in the CPU stub.
Together these fields distinguish payload leaks, wrapper-lifetime leaks, and broader CUDA memory
pressure or fragmentation.
cacheBytes is the device memory held in the buffer reuse cache: dropped buffers awaiting reuse,
which are not counted in liveBytes. cacheCapBytes is the limit selected by
TORCHLEAN_CUDA_CACHE_CAP_BYTES; 0 means unbounded. Both fields are 0 in the CPU stub, which
keeps no cache.
- liveBytes : UInt64
- peakBytes : UInt64
- allocCount : UInt64
- freeCount : UInt64
- wrapperLiveCount : UInt64
- wrapperPeakCount : UInt64
- wrapperAllocCount : UInt64
- wrapperFinalizeCount : UInt64
- deviceFreeBytes : UInt64
- deviceTotalBytes : UInt64
- cacheBytes : UInt64
- cacheCapBytes : UInt64
Instances For
Instances For
Read the current CUDA allocator counters.
token is ignored by the native implementation. It exists so call sites that sample repeatedly
can pass a changing value (for example, the training step), preventing Lean from treating repeated
FFI reads as identical pure expressions.
Instances For
Read the current CUDA allocator counters. Prefer allocatorStatsWithToken in repeated loops.
Instances For
Format a byte count as MiB for allocator progress messages.
Instances For
One-line allocator report for progress logs.
Instances For
Create a device buffer by copying from a host FloatArray (casts each element to float32).
This primitive has a pure Lean type, but the native implementation allocates a fresh device buffer.
Runtime code that repeatedly uploads the same host value should prefer ofFloatArrayIO, which adds
an IO token so two uploads cannot be collapsed into the same external object after one is released.
Effectful host-to-device upload.
The token is ignored by C/CUDA. Its purpose is semantic: repeated uploads of the same FloatArray
must still allocate distinct device buffers. Without a changing token, Lean can treat the extern as
a pure expression, which is not the ownership model we want for long eager CUDA training loops.
Instances For
Copy a buffer back to a host FloatArray (casts float32 elements to Float).
Copy a buffer to its raw float32 byte representation.
This is primarily used by streaming checkpoints. Unlike toFloatArrayIO, it does not widen every
element to Lean Float, so a large CUDA parameter can be written without constructing a second
double-precision host array.
Upload a raw float32 byte payload to a fresh buffer.
Encode a host FloatArray as raw float32 bytes.
Decode raw float32 bytes into a host FloatArray.
Number of float32 elements in the buffer.
Release the device allocation held by a buffer, returning 1 when a live allocation was released.
This is a runtime pressure valve for eager training loops that create many short-lived CUDA buffers. The C finalizer is still safe after an explicit release because the pointer is nulled out.
Effectfully release a device allocation owned by a completed runtime scope.
The changing token makes the release depend on the surrounding IO sequence. Use this form at
ownership boundaries; the pure release primitive is reserved for expressions that thread its
result into another native buffer operation. Every alias becomes invalid, so callers must own the
complete tape or workspace containing the buffer.
Instances For
Release workspace and return keep.
This exists for pure CUDA tape code: because the returned buffer is used downstream, Lean cannot erase the native release call as dead code.
Release a collection of workspace buffers and return keep.
Many CUDA tape formulas create a group of intermediate buffers, then continue with one final result buffer. Threading cleanup through the result keeps ownership local to the formula and avoids waiting for external-object finalizers in long training loops.
Instances For
A CUDA result together with workspace buffers that were needed to compute it.
This is the common ownership shape for eager CUDA formulas. Some forward computations need intermediate buffers again during the backward pass, so the tape keeps those buffers on the node and releases them when the node is retired. Backward formulas use the same shape when they recompute a value only to differentiate through it.
- value : Buffer
Instances For
Return keep after releasing all workspace buffers owned by this result.
Instances For
Return keep after releasing both the result buffer and its workspace buffers.
Instances For
Ask the Lean runtime allocator (mimalloc) to collect abandoned/free pages.
This allocator-only operation releases abandoned or free pages without changing TorchLean values. It is intended for long native eager loops that create many short-lived tape closures and external-buffer wrappers at every step.
In the CUDA build, force = true also releases cached device blocks held by the native buffer pool.
That gives training code a way to trade reuse for returning memory to the CUDA driver at clear
phase boundaries.
Collect the native allocator's free pages.
Instances For
Allocate a length-n buffer filled with zeros.
Deterministic RNG (device-side) #
These are low-level building blocks used by TorchLean's seeded RNG ops (rand_uniform,
bernoulli_mask) when running on the eager CUDA backend.
They use the same SplitMix64-style mixing as TorchLean.Random so results are
deterministic given (seed, counter) and a row-major linear index.
Deterministic U[0,1) generator: returns a length-n buffer (float32) keyed by key.
Absolute value applied pointwise to a CUDA buffer.
Backward for abs: dx = sign(x) * dLdy (with sign(0)=0).
Backward for sqrt.
Uses the TorchLean convention: dx = dLdy * (1 / (2*sqrt(x))) for x > 0, else 0.
Reciprocal: 1/x.
Pointwise maximum of two equal-length CUDA buffers.
Pointwise division of two equal-length CUDA buffers.
Pointwise ReLU activation on a CUDA buffer.
Backward for relu: dx = dLdy where x > 0, else 0.
Tanh-approximate GELU evaluated by one pointwise CUDA kernel.
Backward for tanh-approximate GELU using Activation.geluDerivSpec.
Elementwise addition (sizes must match).
Elementwise subtraction (sizes must match).
Elementwise multiplication (sizes must match).
Device-to-device copy, implemented as a scale-by-one kernel.
Instances For
Copy a buffer and release the source after the copy has been produced.
The native operation creates the destination before it retires the source, so the compiler cannot reorder the two lifetime events. Use this at ownership-transfer boundaries in the sparse CUDA tape.
Perform one Adam-family update in a single CUDA pass.
The result is (parameters, firstMoment, secondMoment). Passing decay = 0 gives Adam; passing
decay = -(learningRate * weightDecay) gives AdamW's decoupled parameter decay. The caller
computes the two bias-correction scales from the step counter, exactly as in Optim.Adam.update
and Optim.AdamW.update.
This primitive changes only the execution plan. TorchLean's optimizer definitions remain the semantic reference, while this native boundary avoids materializing every intermediate tensor in the pointwise update.
Reductions (return a length-1 buffer).