portable-simd
src
portable-simd | src | |
---|---|---|
19 | 745 | |
816 | 3,044 | |
2.0% | 0.7% | |
8.7 | 10.0 | |
21 days ago | 1 day ago | |
Rust | C | |
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
portable-simd
- Rust-lang/portable-SIMD: The testing ground for the future of portable SIMD
-
Let's thank who have helped us in the Rust Community together!
Jubilee and Caleb Zulawski for their tireless work on the portable SIMD project. It will land, some day, and when it does it's going to be an amazing boon for the project.
-
Mutually aligned vectors?
The portable SIMD project implements an as_simd() function for slices. The basics are that you get 3 slices and the middle one is a SIMD slice. It allows for fast aligned loads of the data, which could matter if your algorithm is becoming memory bound; it is also a convenient and safe abstraction. In my case, I actually have 2 vectors (say, x and y). I can take them apart using as_simd() like so:
- Code review: deinterlacing a RGBA colour buffer with std::simd
-
Base64 Encoding Performance: Java vs Rust
Rust has generics and monomorphization. You can write the algorithm once and compile for multiple targets. rust-lang/portable-simd
-
Zen4's AVX512 Teardown
This Rust issue [0] was the best short summary of what an SIMD Shuffle is I could find:
„A "shuffle", in SIMD terms, takes a SIMD vector (or possibly two vectors) and a pattern of source lane indexes (usually as an immediate), and then produces a new SIMD vector where the output is the source lane values in the pattern given.“
[0] https://github.com/rust-lang/portable-simd/issues/11
-
possibility of blas natively in Rust
Yet by default it generates code which is only compatible with Pentium4 or newer. In fact lots of serious issues relate to older CPUs and rustc developers plan is to declare them closed when they would be able to drop i686 support (all AMD CPUs which support SSE2 support x86-64, too while Intel situation is mess).
-
Best portable simd library for stable rust?
The standard API crate for portable simd is at https://github.com/rust-lang/portable-simd, but using this requires nightly, which I don't want to do. I'd like to use a crate for simd that works on both x86_64 and wasm in stable rust. wide looks fine for this purpose. Are there any potentially better choices?
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
See: https://github.com/rust-lang/portable-simd
-
Hey Rustaceans! Got a question? Ask here! (28/2022)!
As for portable SIMD, there's relatively recent activity (last commit 20 days ago) on this repository: https://github.com/rust-lang/portable-simd
src
-
OpenBSD Upgrade 7.3 to 7.4
The OpenBSD project released 7.4 of their OS on 16 Oct 2023 as their 55th release 💫
-
OpenBSD System-Call Pinning
Well since https://www.openbsd.org/ still says
> Only two remote holes in the default install, in a heck of a long time!
I'm assuming not, but I could always be mistaken.
- Project Bluefin: an immutable, developer-focused, Cloud-native Linux
-
From Nand to Tetris: Building a Modern Computer from First Principles
> building a cat from scratch
> That would be an interesting project.
Here is the source code of the OpenBSD implementation of cat:
> https://github.com/openbsd/src/blob/master/bin/cat/cat.c
and here of the GNU coreutils implementation:
> https://github.com/coreutils/coreutils/blob/master/src/cat.c
Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)
-
OpenBSD – pinning all system calls
> I don't know how they define `MAX`, but I'm guessing it's a typical "a>b?a:b"
Indeed: https://github.com/openbsd/src/blob/master/sys/sys/param.h#L...
> Then `SYS_kbind` seems to be a signed int.
It's an untyped #define: https://github.com/openbsd/src/blob/master/sys/sys/syscall.h...
I believe your whole analysis is correct, that running an elf file with an openbsd.syscalls entry with .sysno > INT_MAX will allow an out-of-bounds write.
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
tmux causing ANSI color-response garbage on attaching?
I can reproduce it. And this is the commit that causes the issue: https://github.com/openbsd/src/commit/d21788ce70be80e9c4ed0c52c149e01147c4a823
-
Sudo-rs' first security audit
This doesn’t really change your conclusion, but I think that’s the wrong file. This is the real doas afaict: https://github.com/openbsd/src/blob/master/usr.bin/doas/doas...
Still just a tidy 1072 lines in that folder though.
I spent 5 minutes staring at your file trying to understand how on earth it does the things in the man page, but of course it doesn’t.
-
OpenBSD: Removing syscall(2) from libc and kernel
OpenBSD developers are making serious effort to kill off indirect syscalls, the base system is completely clean, take a look at the work Andrew Fresh did to adapt Perl. He write a complete syscall "dispatcher" or emulator for the Perl syscall function so that it calls the libc stubs.
https://github.com/openbsd/src/commit/312e26c80be876012ae979...
The ports tree is also being cleansed of syscall(2) usage, until they're all gone.
msyscall, pinsyscall, recent mandatory IBT/BTI, xonly. OpenBSD is making waves, but people aren't really seeing them yet.
-
"<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
Actually, I got it wrong, too many vulnerabilities in flight. They did fix it: https://github.com/openbsd/src/commit/375ccafb2eb77de6cf240e...
What are some alternatives?
fast_image_resize - Rust library for fast image resizing with using of SIMD instructions.
cosmopolitan - build-once run-anywhere c library
rust-base64 - base64, in rust
bastille - Bastille is an open-source system for automating deployment and management of containerized applications on FreeBSD.
faster-hex - fast hex
buttersink - Buttersink is like rsync for btrfs snapshots
config-rs - ⚙️ Layered configuration system for Rust applications (with strong support for 12-factor applications).
PHPT - The PHP Interpreter
cargo-about - 📜 Cargo plugin to generate list of all licenses for a crate 🦀
Joomla! - Home of the Joomla! Content Management System
ulid-rs - This is a Rust implementation of the ulid project
ctl - The C Template Library