|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0 |
|
| #
74efac71 |
| 29-Jul-2025 |
Doru Blânzeanu <[email protected]> |
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`
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 only
Signed-off-by: Doru Blânzeanu <[email protected]>
* 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 enabled
Signed-off-by: Doru Blânzeanu <[email protected]>
---------
Signed-off-by: Doru Blânzeanu <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>
show more ...
|
|
Revision tags: v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0 |
|
| #
4c8edb95 |
| 06-Jun-2025 |
Alex Crichton <[email protected]> |
More clearly flag internal crates as such (#10963)
* More clearly flag internal crates as such
This commit is an attempt to more clearly flag internal crates in this
project as internal and not int
More clearly flag internal crates as such (#10963)
* More clearly flag internal crates as such
This commit is an attempt to more clearly flag internal crates in this
project 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 to
be crystal clear from a project perspective that usage of these crates
are highly discouraged and not supported. We'll still probably get such
advisories but we won't be considering them CVEs from the project itself
due to the internal nature of these crates and the discouraging
warnings.
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-fiber
prtest:full
* Update publish script
* Another fiber rename
* Fix some doc tests
show more ...
|
|
Revision tags: v33.0.0, v32.0.0, v31.0.0, v30.0.2, v30.0.1, v30.0.0, v29.0.1, v29.0.0, v28.0.1, v28.0.0, v27.0.0, v26.0.1, v25.0.3, v24.0.2, v26.0.0, v21.0.2, v22.0.1, v23.0.3, v25.0.2, v24.0.1, v25.0.1, v25.0.0, v24.0.0, v23.0.2, v23.0.1, v23.0.0, v22.0.0, v21.0.1, v21.0.0, v20.0.2, v20.0.1, v20.0.0, v17.0.3, v19.0.2, v18.0.4, v19.0.1, v19.0.0, v18.0.3, v18.0.2, v17.0.2, v18.0.1, v18.0.0, v17.0.1, v17.0.0, v16.0.0, v15.0.1, v15.0.0, v14.0.4, v14.0.3, v14.0.2, v13.0.1, v14.0.1, v14.0.0, minimum-viable-wasi-proxy-serve, v13.0.0, v12.0.2, v11.0.2, v10.0.2, v12.0.1, v12.0.0, v11.0.1, v11.0.0, v10.0.1, v10.0.0, v9.0.4, v9.0.3, v9.0.2, v9.0.1, v9.0.0, v6.0.2, v7.0.1, v8.0.1, v8.0.0, v7.0.0, v6.0.1, v5.0.1, v4.0.1, v6.0.0, v5.0.0, v4.0.0, v3.0.1, v3.0.0, v1.0.2, v2.0.2, v2.0.1, v2.0.0, v1.0.1, v1.0.0, v0.40.1, v0.40.0, v0.39.1, v0.38.3, v0.38.2, v0.39.0, v0.38.1, v0.38.0, v0.37.0, v0.36.0, v0.35.3, v0.34.2, v0.35.2, v0.35.1, v0.35.0 |
|
| #
4ed353a7 |
| 22-Feb-2022 |
bjorn3 <[email protected]> |
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
*
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
show more ...
|