ctz

No notifications means if it gets stuck it stays there.

No mapping means if it doesn't fully clean the space (eg, a door is closed) then I have no way of knowing without baby-sitting it.

No keep-out zones means every clean involves carefully preparing the space to hang up trailing wires out of the way -- previously I just had some keep-outs near the wires and that worked perfectly.

Without all these features I have stopped using it; it is quicker to just use a stick vacuum.

Interested! Some detail on how you achieve this for free would be great.

edit: video if you prefer - https://www.youtube.com/watch?v=nJxENYdsB6c

FWIW there is a similar effort for Rust using cranelift: <https://github.com/rust-lang/rustc_codegen_cranelift>

As a side-note, I believe the CPU we tested this on does not suffer from the AVX-512 power limits reported with earlier AVX-512 parts. https://travisdowns.github.io/blog/2020/08/19/icl-avx512-fre... seems to confirm that.

  Runtime errors surface when a program
  runs into an unexpected condition or situation
  such as dividing by zero, memory overflow, or
  addressing a wrong or unauthorized memory
  location or device, or when a program tries to
  perform an illegitimate or unauthorized operation
  or tries to access a library, for example.
  The programs must be thoroughly tested for
  various types of inputs (valid data sets, invalid
  data sets and boundary value data sets) and
  conditions to identify these errors. Once identified,
  runtime errors are easy to fix.

Whereas the separate small allocations will likely end up close together, which gives a better chance that a given cache line will contain several rather than just one.

I mean, in the intervening period there was OpenSSL 3 which was a large backwards-incompatible (API and ABI) release, with a huge amount of effort on the part of OpenSSL developers and users to follow along. It was the ideal opportunity to drop this sort of old stuff.