This note documents a practical experiment with ISPC on Windows: compiling a simple SIMD kernel, exporting it from a DLL, generating an import library, and calling it from Rust and LabVIEW. The goal is to compare ISPC’s generated AVX2 code with native Rust and LabVIEW implementations and to examine the generated assembly.
I have seen many posts about “zero-cost abstractions.” Let’s look at this more carefully — this makes for a good technical exercise.
New Windows feature available in KB5094126.
Command to test in qemu.
An easiest way — from registry.
A simple exercise — how to develop the smallest possible Hello World application.
A simple exercise — how to obtain the CPU base frequency.
A simple exercise — how to obtain the CPU base frequency.
A simple exercise — how to obtain the CPU brand string using CPUID in Rust and pass it to LabVIEW.
A curated list of RustRover hotkeys that help me code faster and stay focused. This is a living collection — I’ll continue updating it as I discover new and useful shortcuts.
When iterating diagonals of a 3D array, the performance differences between LabVIEW and Rust become very noticeable. Even with a straightforward implementation, the generated machine code tells a story about what’s happening under the hood.
Rust’s borrow checker guarantees memory safety at compile time, but some rules—especially around raw pointers—are too subtle for the compiler alone. That’s where Miri comes in. In this post, we’ll walk through two tiny Rust programs: one that Miri accepts, and one that Miri flags as Undefined Behavior. The difference comes down to how Stacked Borrows tracks pointer permissions.
Modern CPUs are fast—but some instructions still hide surprising costs. One of the most misunderstood is DIV. Is 32‑bit division faster than 64‑bit? Does instruction width matter anymore on x86‑64?
To answer this properly, we need more than wall‑clock timers. We need cycle counters, instruction retirement statistics, serialization barriers, and tight control over CPU affinity.
From the administrator command prompt type manage-bde -protectors -get <drive letter>: where
Time to time, and especially for learning purposes, it’s useful to inspect the internal representations that the Rust compiler generates. Below are some notes on how to do that.