Changes in lib.rs

74efac71 - Allow compiling debug-builtins in no_std environment to enable gdb jit (#11304)

Tue, 29 Jul 2025 20:20:31 +0000

Allow compiling debug-builtins in no_std environment to enable gdb jit (#11304)* Allow compiling debug-builtins in no_std environment to enable gdb jit- Make jit-debug crate #![no_std] when `std` feature is not enabled- Make gdb_jit_int module build in no_std environment- Use std when perf_jitdebug is enabled because the perf_jitdebug module does not run in no_std environment- Change debug-builtins feature to only enable gdb_jit_int- The perf_jitdebug feature is enabled in profiling mode onlySigned-off-by: Doru Blânzeanu * Remove feature listing from `default`These are otherwise present via `std`.* Shuffle around some features* Enable `wasmtime-jit-debug/std` from wasmtime's `std` feature* Only enable `perf_jitdump` from `profiling` as that's all that's explicitly needed.* Remove empty features list* Cut down on some `#[cfg]` usage* Update comments in gdb_jit_int module* Add CI checks that `debug-builtins` builds on no_std* Fix missing has_host_compiler_backend when debug-builtins enabledSigned-off-by: Doru Blânzeanu ---------Signed-off-by: Doru Blânzeanu Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/jit-debug/src/lib.rs

4c8edb95 - More clearly flag internal crates as such (#10963)

Fri, 06 Jun 2025 21:13:36 +0000

More clearly flag internal crates as such (#10963)* More clearly flag internal crates as suchThis commit is an attempt to more clearly flag internal crates in thisproject as internal and not intended for external use. Specifically:* Many crates are renamed from `wasmtime-foo` to `wasmtime-internal-foo`.* All of these crates now have `INTERNAL: ...` in their crates.io description.* All of these crates now have a warning at the top of their documentation discouraging use.This change is a result of rustsec/advisory-db#1999 where the goal is tobe crystal clear from a project perspective that usage of these cratesare highly discouraged and not supported. We'll still probably get suchadvisories but we won't be considering them CVEs from the project itselfdue to the internal nature of these crates and the discouragingwarnings.Some concrete changes used here are:* Inter-crate dependencies still use `wasmtime_foo` for naming and do so with Cargo's package-renaming features.* Crate renames are specified at the workspace level so the rename is only in one locations and all other inherit it.* Contribution documentation now has some brief guidelines about crate organization.* Update vet config* Update checks for wasmtime-fiberprtest:full* Update publish script* Another fiber rename* Fix some doc tests List of files: /wasmtime-44.0.1/crates/jit-debug/src/lib.rs

4ed353a7 - Extract jit_int.rs and most of jitdump_linux.rs for use outside of wasmtime (#2744)

Tue, 22 Feb 2022 17:23:44 +0000

Extract jit_int.rs and most of jitdump_linux.rs for use outside of wasmtime (#2744)* Extract gdb jit_int into wasmtime-jit-debug * Move a big chunk of the jitdump code to wasmtime-jit-debug * Fix doc markdown in perf_jitdump.rs List of files: /wasmtime-44.0.1/crates/jit-debug/src/lib.rs