ldivide — Divide the second array by the first, element by element.
ldivide(A, B) and A .\ B compute B ./ A. The implementation applies compatible singleton expansion and covers floating-point, complex, fixed-width integer, logical, character, symbolic, and provider-resident operands under their documented class rules.
Syntax
C = ldivide(A, B)
C = ldivide(A, B, "like", prototype)Inputs
A- Type
Any- Required
- Yes
- Description
- First numeric, logical, character, symbolic, sparse, or provider-resident operand.
B- Type
Any- Required
- Yes
- Description
- Second operand with a size compatible for implicit expansion.
like- Type
StringScalar- Required
- Yes
- Description
- Literal `like` selector for the RunMat output-prototype extension.
prototype- Type
LikePrototype- Required
- Yes
- Description
- Host, device, real, or complex output prototype.
Returns
C- Type
NumericArray- Description
- Element-wise result with the broadcasted operand shape.
Errors
RunMat:ldivide:TooManyOutputs- When
- More than one output is requested.
- Message
ldivide: too many output arguments
RunMat:ldivide:InvalidArgument- When
- Optional arguments are malformed or unsupported.
- Message
ldivide: invalid argument
RunMat:ldivide:InvalidInput- When
- Operands or prototypes cannot be converted into supported numeric or symbolic forms.
- Message
ldivide: invalid input
Operand direction and expansion
The first input is the divisor and the second is the numerator. Equal dimensions align directly, and singleton dimensions expand when all non-singleton extents are compatible. Incompatible dimensions produce a size-mismatch error; compatible empty dimensions remain empty in the broadcasted shape.
Logical inputs contribute zero or one, and character arrays contribute Unicode code points. String arrays and other nonnumeric containers are rejected. Mixed real and complex inputs return a complex quotient.
Classes and numerical behavior
Double floating-point inputs produce double output. If either floating-point input is single, the result uses single or complex-single storage. Because ldivide(A, B) computes B ./ A, zero behavior is determined by zero values in A.
Matching fixed-width integer classes preserve that class. One integer operand may instead be paired with scalar double. Integer quotients round to nearest with half ties away from zero and saturate at the destination bounds. Complex integer arithmetic is rejected.
Provider execution and fusion
Provider hooks receive the numerator before the denominator. A common provider can execute matching resident pairs, real scalar forms, exact typed-integer forms, and supported singleton expansion. Returned handles are validated for owner, device, storage kind, class, precision, shape, and non-aliasing.
Unsupported forms gather through their owning provider and execute the same host contract. Explicit device intent is restored to the selected provider or the call fails; automatic placement may safely return a host value. Compatible floating-point expressions remain eligible for element-wise fusion.
Output prototype extension
RunMat mode accepts ldivide(A, B, 'like', prototype). The prototype selects host or provider residency and can request complex output. MATLAB compatibility mode rejects this extension before execution.
Examples
Left-divide a vector by a scalar
A = 2;
B = [4 6 8];
Q = ldivide(A, B)Expected output:
Q = [2 3 4]Expand column divisors and row numerators
A = (1:3)';
B = [10 20 40];
Q = ldivide(A, B)Expected output:
Q = B ./ ALeft-divide complex values
A = [1+2i, 3-4i];
B = [2-1i, -1+1i];
Q = ldivide(A, B)Expected output:
Q = B ./ AUse character code points as divisors
Q = ldivide('ABC', 2)Expected output:
Q = 2 ./ [65 66 67]Compute reciprocals
A = [1 2 4 8];
Q = ldivide(A, 1)Expected output:
Q = [1 0.5 0.25 0.125]Request a provider-resident left quotient
prototype = gpuArray(single(0));
A = gpuArray(single([2 4 8 16]));
B = gpuArray(single([4 8 16 32]));
Q = ldivide(A, B, 'like', prototype);
R = gather(Q)Expected output:
R = single([2 2 2 2])Using ldivide with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how ldivide changes the result.
Run a small ldivide example, explain the result, then change one input and compare the output.
FAQ
Which input is divided by which?⌄
ldivide(A, B) computes B ./ A: A is the divisor and B is the numerator.
Does ldivide support implicit expansion?⌄
Yes. Singleton dimensions expand automatically; incompatible non-singleton dimensions produce a size-mismatch error.
What numeric class does ldivide return?⌄
Floating-point output is double unless single data participates. Complex inputs produce the corresponding complex floating class. Supported integer forms preserve their integer class.
How does division by zero behave?⌄
Because the call computes B ./ A, zero divisors are zero values in A. Floating-point results follow IEEE-754 signed-infinity and NaN rules.
Can a provider-resident array be combined with a host scalar?⌄
Yes for supported real scalar forms. The runtime selects scalar division in the correct numerator/denominator direction or uploads an exact scalar in the resident integer class.
What happens when provider execution is unavailable?⌄
RunMat gathers through the owner, evaluates the host contract, and restores explicit device intent. Automatic placement may return a host value when that is the safe result.
How can I request provider-resident output?⌄
In RunMat mode, pass 'like' and a provider-resident prototype. The result is validated on that provider or the call returns an error.
How are empty arrays handled?⌄
Compatible empty dimensions propagate into the broadcasted output shape, and the result contains no elements.
Are integers and logical values supported?⌄
Logical values enter floating-point division. Matching integer classes, or one integer operand with scalar double, preserve the integer class and use nearest ties-away rounding with saturation.
Can real and complex operands be mixed?⌄
Yes. The result uses the corresponding complex floating class and the same singleton-expansion rules.
Related Math functions
Elementwise
abs · angle · besselj · bsxfun · complex · conj · double · eps · erf · erfcinv · exp · expm1 · flintmax · gamma · gammaln · heaviside · hypot · imag · int16 · int32 · int64 · int8 · intmax · intmin · log · log10 · log1p · log2 · minus · nextpow2 · plus · pow2 · power · rdivide · real · realmax · realmin · realsqrt · rescale · sign · single · sqrt · times · typecast · uint16 · uint32 · uint64 · uint8
Optim
acceptancesa · annealingboltz · annealingfast · coneprog · crossoverarithmetic · crossoverheuristic · crossoverintermediate · crossoverlaplace · crossoverscattered · crossoversinglepoint · crossovertwopoint · eqnproblem · EquationProblem.solve · EquationProblem.subsasgn · EquationProblem.subsref · evaluate · fgoalattain · fitscalingprop · fitscalingrank · fitscalingshiftlinear · fitscalingtop · fminbnd · fmincon · fminimax · fminsearch · fminunc · fseminf · fsolve · fzero · ga · gacreationlinearfeasible · gacreationnonlinearfeasible · gacreationsobol · gacreationuniform · gacreationuniformint · gaplotbestf · gaplotbestindiv · gaplotdistance · gaplotexpectation · gaplotgenealogy · gaplotmaxconstr · gaplotrange · gaplotscorediversity · gaplotscores · gaplotselection · gaplotstopping · integerConstraint · integral · intlinprog · linprog · lsqcurvefit · lsqlin · LsqlinWarmStart.subsasgn · LsqlinWarmStart.subsref · lsqnonlin · lsqnonneg · mutationadaptfeasible · mutationgaussian · mutationpositivebasis · mutationpower · mutationuniform · optimexpr · optimget · OptimizationConstraint.evaluate · OptimizationConstraint.subsasgn · OptimizationConstraint.subsref · OptimizationExitflag.double · OptimizationExitflag.eq · OptimizationExitflag.ne · OptimizationExitflag.string · OptimizationExpression.acos · OptimizationExpression.acosh · OptimizationExpression.acot · OptimizationExpression.acoth · OptimizationExpression.acsc · OptimizationExpression.acsch · OptimizationExpression.asec · OptimizationExpression.asech · OptimizationExpression.asin · OptimizationExpression.asinh · OptimizationExpression.atan · OptimizationExpression.atanh · OptimizationExpression.cat · OptimizationExpression.cos · OptimizationExpression.cosh · OptimizationExpression.cot · OptimizationExpression.coth · OptimizationExpression.csc · OptimizationExpression.csch · OptimizationExpression.ctranspose · OptimizationExpression.cumprod · OptimizationExpression.cumsum · OptimizationExpression.diag · OptimizationExpression.diff · OptimizationExpression.dot · OptimizationExpression.eq · OptimizationExpression.evaluate · OptimizationExpression.exp · OptimizationExpression.ge · OptimizationExpression.horzcat · OptimizationExpression.ldivide · OptimizationExpression.le · OptimizationExpression.log · OptimizationExpression.mean · OptimizationExpression.minus · OptimizationExpression.mldivide · OptimizationExpression.mpower · OptimizationExpression.mrdivide · OptimizationExpression.mtimes · OptimizationExpression.norm · OptimizationExpression.plus · OptimizationExpression.power · OptimizationExpression.prod · OptimizationExpression.rdivide · OptimizationExpression.reshape · OptimizationExpression.sec · OptimizationExpression.sech · OptimizationExpression.sin · OptimizationExpression.sinh · OptimizationExpression.sqrt · OptimizationExpression.subsasgn · OptimizationExpression.subsref · OptimizationExpression.sum · OptimizationExpression.tan · OptimizationExpression.tanh · OptimizationExpression.times · OptimizationExpression.trace · OptimizationExpression.transpose · OptimizationExpression.uminus · OptimizationExpression.uplus · OptimizationExpression.vertcat · OptimizationExpression.zeros · OptimizationExpression.zerosLike · OptimizationProblem.solve · OptimizationProblem.subsasgn · OptimizationProblem.subsref · OptimizationVariable.subsasgn · OptimizationVariable.subsref · optimoptions · optimplotconstrviolation · optimplotfirstorderopt · optimplotfunccount · optimplotfval · optimplotfvalconstr · optimplotmilp · optimplotstepsize · optimplotx · optimproblem · optimset · optimvar · optimwarmstart · particleswarm · patternsearch · psplotbestf · psplotbestx · psplotfuncount · psplotmaxconstr · psplotmeshsize · pswcreationuniform · pswplotbestf · quad · quadprog · QuadprogWarmStart.subsasgn · QuadprogWarmStart.subsref · saplotbestf · saplotbestx · saplotf · saplotstopping · saplottemperature · saplotx · savemilpsolutions · secondordercone · selectionremainder · selectionroulette · selectionstochunif · selectiontournament · selectionuniform · simulannealbnd · solve · surrogateopt · surrogateoptplot · temperatureboltz · temperatureexp · temperaturefast
Trigonometry
acos · acosd · acosh · acotd · acscd · asecd · asin · asind · asinh · atan · atan2 · atan2d · atand · 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
Factor
chol · decomposition · decomposition.ctranspose · decomposition.mldivide · decomposition.mrdivide · decomposition.mtimes · decomposition.rdivide · decomposition.subsref · decomposition.times · decomposition.uminus · decomposition.uplus · eig · eigs · gmres · ichol · ilu · lu · ordeig · ordqz · ordschur · pcg · qr · qz · rsf2csf · schur · svd
Ops
cross · ctranspose · dot · mldivide · mpower · mrdivide · mtimes · pagemtimes · pagetranspose · trace · transpose
Interpolation
griddedInterpolant · griddedInterpolant.subsref · interp1 · interp1q · interp2 · pchip · ppval · spline
Integer Division
Source you can read
Every RunMat function's source is public. Read exactly how ldivide is executed, line by line, in Rust.
- View the source for ldivide in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/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.