RunMat
  • Pricing
RunMat
GitHub
GitHub
DownloadSign InTry in Browser
DesktopRuntimeServer
RunMat

Run math blazing fast

GitHubX (Twitter)LinkedIn

Company

  • About
  • Pricing
  • Contact

Explore

  • RunMat for academia
  • RunMat vs MATLAB Online
  • Benchmarks

Get product updates and release notes from the RunMat team.

© 2026 Dystr · Made withfor the scientific community.

RunMat™ is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

LicensePrivacy
/
See all docs
Builtin Reference
    • abs
    • angle
    • bsxfun
    • complex
    • conj
    • double
    • erf
    • erfcinv
    • exp
    • expm1
    • factorial
    • flintmax
    • gamma
    • gammaln
    • heaviside
    • hypot
    • idivide
    • imag
    • intmax
    • intmin
    • ldivide
    • log
    • log10
    • log1p
    • log2
    • minus
    • nextpow2
    • plus
    • pow2
    • power
    • rdivide
    • real
    • realmax
    • realmin
    • realsqrt
    • rescale
    • sign
    • single
    • sqrt
    • swapbytes
    • times
    • typecast
    • uint16
    • uint32
    • uint8

plus — Compute element-wise addition in MATLAB and RunMat.

plus(A, B) (or A + B) adds corresponding elements of A and B. Implicit expansion, complex handling, and output-shape behavior follow MATLAB semantics.

Syntax

C = plus(A, B)
C = plus(A, B, "like", prototype)

Inputs

NameTypeRequiredDefaultDescription
AAnyYes—Left numeric/logical operand.
BAnyYes—Right numeric/logical operand.
likeStringScalarYes—Literal string "like".
prototypeLikePrototypeYes—Output class/device prototype.

Returns

NameTypeDescription
CNumericArrayElementwise sum result.

Errors

IdentifierWhenMessage
RunMat:plus:InvalidArgumentOptional arguments are malformed or unsupported.plus: invalid argument
RunMat:plus:InvalidInputOperands or prototypes cannot be converted into supported numeric/logical forms.plus: invalid input
RunMat:plus:SizeMismatchOperands are not broadcast-compatible.plus: array sizes are not compatible for broadcasting
RunMat:plus:InternalProvider interaction, gather/upload, or internal tensor construction failed.plus: internal error
RunMat:plus:SparseSizeMismatchSparse operands cannot be implicitly expanded to a compatible result shape.plus: sparse operand sizes are not compatible
RunMat:plus:SparseUnsupportedOperandSparse arithmetic is requested with an unsupported operand class or residency.plus: unsupported sparse arithmetic operand
RunMat:plus:SparseDensifyTooLargeA sparse operation would have to materialize a dense or fully populated sparse result beyond the runtime limit.plus: sparse arithmetic result is too large to materialize
RunMat:plus:SparseInternalSparse arithmetic storage construction or conversion failed unexpectedly.plus: sparse arithmetic internal error

How plus works

  • Supports real, complex, logical, and character inputs; logical and character data are promoted to double precision before addition.
  • Implicit expansion works across any dimension, provided the non-singleton extents match. Size mismatches raise the standard MATLAB-compatible error message.
  • Complex operands follow MATLAB's analytic rule (a + ib) + (c + id) = (a + c) + i(b + d).
  • Empty dimensions propagate naturally—if either operand has a zero-sized dimension after broadcasting, the result is empty with the broadcasted shape.
  • Integer addition preserves the integer class. The other operand must use the same integer class or be scalar double; fractional results round, overflow saturates, and 64-bit integer/scalar-double arithmetic uses the extended-precision compatibility path.
  • Sparse real matrices interoperate with sparse, dense, logical, character, scalar, and complex operands. Sparse-sparse addition preserves sparse storage; dense, nonzero scalar, and complex interop returns full real or complex storage when implicit zeros become nonzero.
  • In RunMat compatibility mode, the RunMat-only optional 'like' prototype makes the output adopt the residency and complexity characteristics of the prototype. MATLAB-compatible mode rejects this extension before dispatch.

Does RunMat run plus on the GPU?

When a gpuArray provider is active:

1. If both operands are gpuArrays with identical shapes, RunMat dispatches to the provider's elem_add hook, including for complex-interleaved resident handles. 2. If one operand is a real scalar and the other is a gpuArray, the runtime calls scalar_add to keep the result on the device. 3. For shape-compatible implicit expansion, RunMat first expands gpuArray operands on device with repmat and then dispatches elem_add. 4. The fusion planner treats plus as a fusible elementwise node, so adjacent elementwise producers/consumers can execute inside a single WGSL kernel or provider-optimised pipeline, avoiding spurious host↔device transfers. 5. Unsupported shapes or operand kinds gather transparently to host memory, compute the result with full MATLAB semantics, and return a host tensor unless a 'like' GPU prototype is supplied—in which case the runtime re-uploads the output to honour the residency request.

GPU memory and residency

RunMat's auto-offload planner keeps tensors on the GPU whenever fused expressions benefit from device execution. Explicit gpuArray / gather calls remain supported for MATLAB code that manages residency manually. When the active provider lacks the kernels needed for a particular call (for example, implicit expansion between gpuArrays of different shapes), RunMat gathers back to the host, computes the MATLAB-accurate result, and resumes execution seamlessly.

Examples

Adding two matrices element-wise

A = [1 2 3; 4 5 6];
B = [7 8 9; 1 2 3];
S = plus(A, B)

Expected output:

S =
     8    10    12
     5     7     9

Adding a scalar to every element of a matrix

A = magic(3);
shifted = plus(A, 0.5)

Expected output:

shifted =
    8.5    1.5    6.5
    3.5    5.5    9.5
   10.5    7.5    2.5

Using implicit expansion between a column and row vector

col = (1:3)';
row = [10 20 30];
m = plus(col, row)

Expected output:

m =
    11    21    31
    12    22    32
    13    23    33

Adding complex inputs element-wise

z1 = [1+2i, 3-4i];
z2 = [2-1i, -1+1i];
sumz = plus(z1, z2)

Expected output:

sumz =
     3 + 1i     2 - 3i

Adding character codes to produce numeric arrays

letters = 'ABC';
codes = plus(letters, 2)

Expected output:

codes = [67 68 69]

Keeping element-wise sums on the GPU with 'like'

proto = gpuArray.zeros(1, 1);
G1 = gpuArray([1 2 3]);
G2 = gpuArray([4 5 6]);
deviceSum = plus(G1, G2, 'like', proto);
result = gather(deviceSum)

Expected output:

deviceSum =
  1x3 gpuArray
     5     7     9
result =
     5     7     9

Using plus with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how plus changes the result.

Run a small plus example, explain the result, then change one input and compare the output.

FAQ

Does plus support MATLAB implicit expansion?⌄

Yes. Any singleton dimensions expand automatically. If a dimension has incompatible non-singleton extents, plus raises the standard size-mismatch error.

What numeric type does plus return?⌄

Ordinary real inputs produce double and complex inputs produce complex double. Integer arithmetic preserves the integer class under MATLAB's same-class-or-scalar-double rules. Logical and character inputs are promoted to double.

Can I add gpuArrays and host scalars?⌄

Yes. RunMat keeps the computation on the GPU when the scalar is numeric. For other host operand types, the runtime gathers the gpuArray and computes on the CPU.

Does plus preserve gpuArray residency after a fallback?⌄

When a fallback occurs (for example, implicit expansion that the provider does not implement), the resulting array stays on the host by default. Provide a 'like', gpuArray(...) prototype if you need the runtime to re-upload the final result automatically.

How can I force the result to stay on the GPU?⌄

Provide a 'like' prototype: plus(A, B, 'like', gpuArray.zeros(1, 1)) keeps the result on the device even if one of the inputs originated on the host.

How are empty arrays handled?⌄

Empty dimensions propagate. If either operand has an extent of zero in the broadcasted shape, the result is empty with that broadcasted shape.

Are integer inputs supported?⌄

Yes. Integer addition preserves the integer class, rounds fractional results, and saturates overflow. Inputs must use the same integer class or pair one integer operand with scalar double.

Can I mix complex and real operands?⌄

Absolutely. The result is complex, with broadcasting rules identical to MATLAB.

Does plus preserve sparse matrices?⌄

Sparse-sparse addition returns sparse storage, including scalar sparse expansion when the result fits the sparse materialization limit. Adding dense, complex, or nonzero full scalar operands returns full storage because implicit sparse zeros become stored nonzero values.

What about string arrays?⌄

RunMat currently rejects string-array plus; MATLAB uses plus to append strings, so this remains a documented non-integer compatibility gap.

Related Math functions

Elementwise

abs · angle · bsxfun · complex · conj · double · erf · erfcinv · exp · expm1 · factorial · flintmax · gamma · gammaln · heaviside · hypot · idivide · imag · intmax · intmin · ldivide · log · log10 · log1p · log2 · minus · nextpow2 · pow2 · power · rdivide · real · realmax · realmin · realsqrt · rescale · sign · single · sqrt · swapbytes · times · typecast · uint16 · uint32 · uint8

Trigonometry

acos · acosh · asin · asinh · atan · atan2 · atanh · cos · cosd · cosh · cospi · deg2rad · pol2cart · rad2deg · sin · sind · sinh · sinpi · tan · tand · tanh

Reduction

all · any · bounds · cummax · cummin · cumprod · cumsum · cumtrapz · diff · gradient · max · maxk · mean · median · min · mink · movmax · movmean · movmedian · movmin · movprod · movstd · movsum · movvar · nnz · prod · rms · std · sum · trapz · var

Structure

bandwidth · isdiag · ishermitian · issymmetric · istril · istriu · symrcm

Signal

blackman · butter · buttord · cheb2ord · conv · conv2 · deconv · downsample · envelope · filter · filtfilt · fir1 · freqz · gauspuls · hamming · hann · hilbert · periodogram · pulstran · pwelch · rectpuls · resample · sawtooth · sinc · spectrogram · square · tripuls · unwrap · upsample · zplane

Rounding

ceil · fix · floor · mod · rem · round

Factor

chol · decomposition · eig · eigs · lu · qr · svd

Solve

cond · det · inv · linsolve · norm · null · pinv · rank · rcond · rref · vecnorm

Optim

coneprog · fminbnd · fminunc · fsolve · fzero · integral · linprog · lsqcurvefit · lsqnonlin · optimoptions · optimset · quad · secondordercone

Ops

cross · ctranspose · dot · mldivide · mpower · mrdivide · mtimes · pagemtimes · pagetranspose · trace · transpose

Symbolic

digits · int · limit · piecewise · sym · syms · vpa

Fft

fft · fft2 · fftn · fftshift · ifft · ifft2 · ifftn · ifftshift

Interpolation

griddedInterpolant · interp1 · interp1q · interp2 · pchip · ppval · spline

Discrete

lcm · primes

Ode

ode15s · ode23 · ode45

Poly

polyder · polyfit · polyint · polyval · roots

Open-source implementation

Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how plus is executed, line by line, in Rust.

  • View the source for plus in Rust on GitHub
  • Learn how the RunMat runtime works
  • Found a bug? Open an issue with a minimal reproduction.

About RunMat

RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 license.

  • RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
  • Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.

Download RunMatOpen Sandbox
On this page
  • Syntax
  • Inputs
  • Returns
  • Errors
  • How plus works
  • Does RunMat run plus on the GPU?
  • GPU memory and residency
  • Examples
  • Adding two matrices element-wise
  • Adding a scalar to every element of a matrix
  • Using implicit expansion between a column and row vector
  • Adding complex inputs element-wise
  • Adding character codes to produce numeric arrays
  • Keeping element-wise sums on the GPU with 'like'
  • Using plus with coding agents
  • FAQ
  • Related Math functions
  • Elementwise
  • Trigonometry
  • Reduction
  • Structure
  • Signal
  • Rounding
  • Factor
  • Solve
  • Optim
  • Ops
  • Symbolic
  • Fft
  • Interpolation
  • Discrete
  • Ode
  • Poly
  • Open-source implementation
  • About RunMat