tic — Start a high-resolution session-owned stopwatch.
tic starts a monotonic wall-clock stopwatch. Capture its opaque uint64 token when a later toc(token) must refer to that start; an uncaptured tic only updates the latest start.
Syntax
timerVal = tic()Returns
timerVal- Type
NumericScalar- Description
- Opaque session-owned uint64 stopwatch token used by toc.
Errors
RunMat:tic:ContextUnavailable- When
- No invocation timing context is installed.
- Message
tic: runtime context is unavailable
RunMat:tic:TokenExhausted- When
- The process-local stopwatch token identity space is exhausted.
- Message
tic: stopwatch token identity space exhausted
Behavior
The returned uint64 is an opaque session token, not an encoded timestamp. A token from another session or execution generation is invalid.
tic without an observed output updates only the latest start; repeated statement-form starts do not retain unreachable handles.
tic uses the invocation's monotonic timing service and never enters GPU fusion or provider execution.
Examples
Measuring a simple loop
tic;
for k = 1:1e5
sqrt(k);
end
elapsed = tocCapturing and reusing the tic handle
t = tic;
x = sum(1:1000);
elapsed = toc(t)Nesting timers for staged profiling
outer = tic;
x = sum(1:1000);
inner = tic;
y = sum(1:2000);
innerT = toc(inner);
outerT = toc(outer)Measuring a suspending wait
token = tic;
pause(0.01);
elapsed = toc(token)Resetting the stopwatch after a measurement
elapsed1 = toc(tic);
pause(0.1);
elapsed2 = toc(tic)Using tic with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how tic changes the result.
Run a small tic example, explain the result, then change one input and compare the output.
FAQ
Does tic print anything when called without a semicolon?⌄
No. tic is a sink builtin; the stopwatch token is displayed only when explicitly requested.
Is the returned handle portable across sessions?⌄
No. The opaque token is valid only in its owning RunMat session and cannot be saved for a later session.
Can I run tic on a worker thread?⌄
Yes. Independent runtime contexts own independent stopwatch state; retain explicit tokens when starts may interleave within a context.
How accurate is the measurement?⌄
The monotonic host clock determines resolution; RunMat adds no artificial jitter or throttling.
Does tic participate in GPU fusion?⌄
No. It is a host-side timing boundary.
Related Timing functions
cputime · pause · set.BusyMode · set.ErrorFcn · set.ExecutionMode · set.Name · set.ObjectVisibility · set.Period · set.StartDelay · set.StartFcn · set.StopFcn · set.Tag · set.TasksToExecute · set.TimerFcn · set.UserData · timeit · timer · timerfind · timerfindall · toc
Source you can read
Every RunMat function's source is public. Read exactly how tic is executed, line by line, in Rust.
- View the source for tic 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.