| [package] | |
| name = "compare256-benchmark" | |
| version = "0.1.0" | |
| edition = "2024" | |
| [dev-dependencies] | |
| divan = "0.1.21" | |
| [[bench]] | |
| name = "compare256" |
| #[unsafe(naked)] | |
| extern "C" fn Reset() { | |
| core::arch::naked_asm!( | |
| // debug info | |
| ".cfi_sections .debug_frame", | |
| ".cfi_startproc", | |
| // If enabled, initialise the SP. This is normally initialised by the CPU itself or by a | |
| // bootloader, but some debuggers fail to set it when resetting the target, leading to | |
| // stack corruptions. | |
| #[cfg(feature = "set-sp")] |
| const N: usize = 10000; | |
| fn main() { | |
| let mut args = std::env::args().skip(1); // skip the program name | |
| // just get a bunch of arbitrary values cheaply | |
| const INPUT: &[u8] = include_bytes!( | |
| "/home/folkertdev/.cargo/registry/cache/github.com-1ecc6299db9ec823/clap-4.2.7.crate" | |
| ); | |
| let (_, table, _) = unsafe { INPUT.align_to() }; |
| ```rust | |
| pub fn main() { | |
| for _ in 0..100000 { | |
| for email in INPUT { | |
| let result = autolink_email(core::hint::black_box(email.as_bytes())); | |
| } | |
| } | |
| } | |
| const INPUT: &[&str] = &[ |
| [build] | |
| target = "s390x-unknown-linux-gnu" | |
| [target.s390x-unknown-linux-gnu] | |
| # runner = "qemu-s390x -cpu max -L /usr/s390x-linux-gnu" | |
| runner = "qemu-s390x -cpu qemu,vx=on,vxeh=on,vxeh2=off -L /usr/s390x-linux-gnu" | |
| # runner = "qemu-s390x -cpu z10EC -L /usr/s390x-linux-gnu" | |
| linker = "s390x-linux-gnu-gcc" |
| typedef unsigned char Bool; | |
| typedef unsigned char UChar; | |
| typedef int Int32; | |
| typedef unsigned int UInt32; | |
| #define True ((Bool)1) | |
| #define BZ_X_MAGIC_1 10 | |
| typedef struct { | |
| char *next_in; | |
| } | |
| bz_stream; |
A proof of concept implementation can be found at https://github.com/trifectatechfoundation/rust/tree/labeled-match. Build it with ./x build, and then set up the toolchain. Now cargo +stage1 build should use a compiler with labeled-match available.
git clone https://github.com/trifectatechfoundation/zlib-rs.git
Some further zlib-rs benchmarks using commit c9b7299fa81ca2a8448cbe3e96a42275c9b41b24
Rust will panic when you try to index out of bounds
This check has a cost: your CPU must perform this check. Typically this involves two instructions: a compare "is the index in bounds" and a jump "go to the panic code". Hence, we intuitively expect programs that perform bounds checking to be slightly slower. In theory, C has an edge here because it does not, by default, check that array access is in bounds.
| use std::ffi::{c_int, c_uint}; | |
| // we use the libz_sys but configure zlib-ng in zlib compat mode | |
| use libz_sys as libz_ng_sys; | |
| use zlib_rs::{DeflateFlush, ReturnCode}; | |
| fn main() { | |
| let mut it = std::env::args(); |
| Finished `dev` profile [unoptimized] target(s) in 0.05s | |
| WARNING: The `change-id` is missing in the `config.toml`. This means that you will not be able to track the major changes made to the bootstrap configurations. | |
| NOTE: to silence this warning, add `change-id = 127866` at the top of `config.toml` | |
| Building stage0 library artifacts (x86_64-unknown-linux-gnu) | |
| Finished `release` profile [optimized + debuginfo] target(s) in 0.11s | |
| Building compiler artifacts (stage0 -> stage1, x86_64-unknown-linux-gnu) | |
| Finished `release` profile [optimized + debuginfo] target(s) in 0.19s | |
| Creating a sysroot for stage1 compiler (use `rustup toolchain link 'name' build/host/stage1`) | |
| Building stage0 tool lld-wrapper (x86_64-unknown-linux-gnu) | |
| Finished `release` profile [optimized + debuginfo] target(s) in 0.10s |