Skip to main content

Crate rusty_esp_dsp_esp

Crate rusty_esp_dsp_esp 

Source
Expand description

rusty_esp_dsp-esp — the chip half of the kernel home: the PIE twins.

[PieS3] (feature pie-s3) and [PieP4] (feature pie-p4) implement the seam’s three traits. A kernel with a twin runs the chip’s SIMD; a kernel without one runs the scalar oracle under the same name, so a firmware selects its type in one place and nothing else changes as twins arrive. Every twin is gated byte-identical against rusty_esp_dsp::seam::Scalar over the corpus [rusty_esp_dsp::seam::twin_matches_scalar] generates — on the host with the intrinsics stubbed to scalar, and on the board with them live (D2’s board row).

Nine of the seam’s thirteen kernels now run real ee.* twins on an ESP32-S3 – yuyv_to_gray8, downscale2x_gray8, dot_i16, sum_sq_i16, peak_abs_i16, sad_8x8, sad_16x16, yuyv_to_rgb565 and downscale2x_rgb565. The rest delegate to the oracle, either because no twin exists yet or because one was built and MEASURED WORSE (satd_4x4_sum; see the ledger’s P4 and P6 entries) or is impossible on this unit (rgb565_to_rgb888 and rgb888_to_rgb565 need a 3-way byte deinterleave the ISA does not have).

The twins are cfg(target_arch = "xtensa"). Off-chip – a host build, a host test, a RISC-V target – every method is the scalar oracle, so this crate builds everywhere and needs nightly only for the Xtensa build.

PieP4 still delegates everything: D4 has no board yet.

Functions§

default_kernels
The kernel set a firmware for chip should hold: the chip’s twins when the feature is on, the scalar oracle otherwise. Written as a function so the choice is one line in a firmware and nowhere else.

Type Aliases§

Kernels
What default_kernels returns under the crate’s features.