flexible-vectors

Vector operations for WebAssembly (by WebAssembly)

Flexible-vectors Alternatives

Similar projects and alternatives to flexible-vectors

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better flexible-vectors alternative or higher similarity.

flexible-vectors reviews and mentions

Posts with mentions or reviews of flexible-vectors. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-02.
  • Mojo – a new programming language for all AI developers
    7 projects | news.ycombinator.com | 2 May 2023
    Wonderful language. Only complaint (so far) : SIMD should be named Vector and dispatched to whatever SIMD/vector pipeline the host offers, similar to Flexible Vectors proposal in WASM: https://github.com/WebAssembly/flexible-vectors/blob/main/pr...
  • AVX 512 will be the future
    4 projects | news.ycombinator.com | 28 Nov 2022
    Abstract vectorization instructions in wasm will make life a lot easier

    https://github.com/WebAssembly/flexible-vectors/blob/main/pr... great proposal!

    Mapping to whatever hardware is available as some sort of micro library

  • Take More Screenshots
    24 projects | news.ycombinator.com | 24 Jul 2022
    I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; https://github.com/WebAssembly/flexible-vectors/blob/master/... are a better solution. They are a lot like RVV; https://github.com/riscv/riscv-v-spec, research around vector processing is why RISC-V exists in the first place!

    I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.

    16.5kloc of Rust https://github.com/rhysd/wain

    The most complete wasm env for small devices is wasm3

    20kloc of C https://github.com/wasm3/wasm3

    I get what you are saying as to be so small that there isn't a place of bugs to hide.

    > β€œThere are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare

    Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code; https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...

    I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.

    See, https://copy.sh/v86/

    MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.

    Lua, Typed Assembly; https://en.wikipedia.org/wiki/Typed_assembly_language and Sector Lisp; https://github.com/jart/sectorlisp seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.

    If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.

    https://github.com/WebAssembly/meetings

    When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.

    https://gist.github.com/dabeaz/7d8838b54dba5006c58a40fc28da9...

  • Exploring SIMD performance improvements in WebAssembly
    2 projects | news.ycombinator.com | 2 Feb 2022
    Thanks! Good points, I think in general the fixed-width "packed" SIMD ISAs have the downsides that you mentioned.

    But it seems that WebAssembly doesn't have length-agnostic SIMD instructions yet. There is an open proposal to add this though: https://github.com/WebAssembly/flexible-vectors

  • A note from our sponsor - WorkOS
    workos.com | 29 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more β†’

Stats

Basic flexible-vectors repo stats
4
43
2.8
21 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com