|
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, 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 |
|
| #
8cc276b0 |
| 09-Jun-2025 |
Alex Crichton <[email protected]> |
Enable clippy's `redundant_field_names` lint (#10985)
Seems like a clear enough improvement and also something useful to have
a lint for as refactorings enable/disable this pattern over time, so
thi
Enable clippy's `redundant_field_names` lint (#10985)
Seems like a clear enough improvement and also something useful to have
a lint for as refactorings enable/disable this pattern over time, so
this should help us stay consistent.
show more ...
|
| #
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 |
|
| #
ca5a9db0 |
| 16-Aug-2023 |
ssunkin-fastly <[email protected]> |
Memcheck for Wasm guests in Wasmtime (#6820)
* attempt at inserting things where i think they might belong + questions
* entry hook + questions
* commented out all changes, doc comment errors
* f
Memcheck for Wasm guests in Wasmtime (#6820)
* attempt at inserting things where i think they might belong + questions
* entry hook + questions
* commented out all changes, doc comment errors
* fix doc comment
* libcalls build now!!!!
* initial check_malloc_exit setup
* WIP: load/store hooks
* hooks added + building
* added valgrind library
* made wasm-valgrind accessible in wasmtime
* check_malloc filled in...
* move valgrind_state to an appropriate part of instance
it works!!!!!
* yay it's working! (?) i think??
* stack tracing in progress
* errors + num bytes displayed
* initial valgrind configuration
* valgrind conditional some warnings fixed
* conditional compilation + CLI flag finished
* panic!() changed to bail!()
* started adding doc comments
* added memory grow hook + fixed access size handling
* removed test.wasm
* removed malloc_twice.wat
* doc comments in spec.rs
* pr feedback addressed
* ran cargo fmt
* addressing more feedback
* Remove fuzz crate from wmemcheck.
* Review feedback and test fix.
* add wasmtime-wmemcheck crate to publish allowlist.
* fix build without compiler features
* reorder crates in publish list
* Add trampolines for libcalls on s390x.
* Make wasmtime-wmemcheck dep an exact version requirement.
---------
Co-authored-by: iximeow <[email protected]>
Co-authored-by: Chris Fallin <[email protected]>
Co-authored-by: iximeow <[email protected]>
show more ...
|