Changes in lib.rs

e581aa8b - Implement `IntoIterator` for our OOM-handling `PrimaryMap` (#12605)

Tue, 17 Feb 2026 21:53:59 +0000

Implement `IntoIterator` for our OOM-handling `PrimaryMap` (#12605)* Implement `IntoIterator` for our OOM-handling `PrimaryMap`* rustfmt List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

def5998e - Remove `cranelift_entity::{Signed, Unsigned}` (#11400)

Thu, 07 Aug 2025 23:44:38 +0000

Remove `cranelift_entity::{Signed, Unsigned}` (#11400)Use `*::cast_{un,}signed` in the Rust standard library stabilized in1.87. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

ef48aecd - Fix name qualification in the `entity_impl` macro. (#10776)

Wed, 14 May 2025 21:08:54 +0000

Fix name qualification in the `entity_impl` macro. (#10776)Use `$crate` in the `entity_impl` macro for references to itself, so thatthey resolve even if `entity_impl` isn't imported into the global scope. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

bf9273a3 - `cranelift-frontend`: Propagate needs-stack-map from variables to values during finalization (#10468)

Tue, 25 Mar 2025 19:40:25 +0000

`cranelift-frontend`: Propagate needs-stack-map from variables to values during finalization (#10468)* cranelift-frontend: Propagate needs-stack-map from variables to values during finalizationRather than trying to propagate the needs-stack-map bit from variables to valuesonline, while we are building the IR and defining and using variables, waituntil the function is being finalized, and then propagate everything all atonce. This avoids potential repeated work and is easier to ensure that it iscomplete and covers all values associated with a variable, since by the time weare finalizing the function, we won't add any new values for a variable that wewill need to keep track of and propagate this information to.This also means that we can remove the `params_added_to_blocks` vector from theSSA side effects structure, since it was only used to online-update the`stack_map_values` set.* Initialize the env-logger in `#[wasmtime_test]`* Fix needs-stack-map set iterationFor reasons I do not understand, the `EntitySet::keys` method includes keys thatare not in the set, and we have unit tests asserting this bizarre behavior. Veryperplexing. So I added a new method to iterate over just the elements of theset. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

b09b892c - refactor: unify how bits are accessed in `cranelift-entity` (#10126)

Mon, 27 Jan 2025 22:16:49 +0000

refactor: unify how bits are accessed in `cranelift-entity` (#10126)* refactor: unify how bits are accessed in `cranelift-entity`While using `MachLabel`, a `cranelift-entity`-created type, I noticedthat there were three ways to access the contained bits: `.get()`,`.as_u32()`, and `.as_bits()`. All performed essentially the samefunction and it was unclear which to use.This change removes `MachLabel::get()`, replacing it with `as_u32()`.It also replaces all uses of `from_bits()` and `as_bits()` with`from_u32()` and `as_u32()`. Why? I would have preferred the "bits"naming since it seems more clear ("just unwrap this thing") and it couldavoid a large rename if the type were changed in the future, I realizedthat there are vastly more uses of the "u32" naming that alreadyexist--it's just easier.While this refactoring _should_ result in no functional change, you maynotice a couple of failing tests related to a pre-existing check on`from_u32` that did not exist on `from_bits`. For some reason,`from_u32` asserted that we would never pick `u32::MAX` for an entityvalue; unfortunately, some parsing code, `decode_narrow_field`, doesjust this. Why did we have such an assertion in the first place? Is itstill needed? Should `decode_narrow_field` do something else?* Re-add `from_bits`, `as_bits` and uses* doc: tweak doc comment List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

45b60bd6 - Start using `#[expect]` instead of `#[allow]` (#9696)

Mon, 02 Dec 2024 17:19:20 +0000

Start using `#[expect]` instead of `#[allow]` (#9696)* Start using `#[expect]` instead of `#[allow]`In Rust 1.81, our new MSRV, a new feature was added to Rust to use`#[expect]` to control lint levels. This new lint annotation willsilence a lint but will itself cause a lint if it doesn't actuallysilence anything. This is quite useful to ensure that annotations don'tget stale over time.Another feature is the ability to use a `reason` directive on theattribute with a string explaining why the attribute is there. Thisstring is then rendered in compiler messages if a warning or errorhappens.This commit migrates applies a few changes across the workspace:* Some `#[allow]` are changed to `#[expect]` with a `reason`.* Some `#[allow]` have a `reason` added if the lint conditionally fires (mostly related to macros).* Some `#[allow]` are removed since the lint doesn't actually fire.* The workspace configures `clippy::allow_attributes_without_reason = 'warn'` as a "ratchet" to prevent future regressions.* Many crates are annotated to allow `allow_attributes_without_reason` during this transitionary period.The end-state is that all crates should use`#[expect(..., reason = "...")]` for any lint that unconditionally firesbut is expected. The `#[allow(..., reason = "...")]` lint should be usedfor conditionally firing lints, primarily in macro-related code.The `allow_attributes_without_reason = 'warn'` level is intended to bepermanent but the transitionary`#[expect(clippy::allow_attributes_without_reason)]` crate annotationsto go away over time.* Fix adapter buildprtest:full* Fix one-core build of icache coherence* Use `allow` for missing_docsWork around rust-lang/rust#130021 which was fixed in Rust 1.83 and isn'tfixed for our MSRV at this time.* More MSRV compat List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

d4b6665a - Add a `Signed` trait to match the `Unsigned` trait (#9232)

Thu, 12 Sep 2024 18:52:56 +0000

Add a `Signed` trait to match the `Unsigned` trait (#9232)* Add a `Signed` trait to match the `Unsigned` traitI've wanted to use this every now and then but haven't gotten around toadding this so figured I'd go ahead and add it.* Update cranelift/entity/src/signed.rsCo-authored-by: Nick Fitzgerald ---------Co-authored-by: Nick Fitzgerald List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

a0442ea0 - Enforce `uninlined_format_args` for the workspace (#9065)

Mon, 05 Aug 2024 09:59:59 +0000

Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

1c013e30 - Add support for recursion groups in the types registry (#8404)

Fri, 19 Apr 2024 16:35:57 +0000

Add support for recursion groups in the types registry (#8404) List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

5856590f - Configure workspace lints, enable running some Clippy lints on CI (#7561)

Mon, 20 Nov 2023 23:23:41 +0000

Configure workspace lints, enable running some Clippy lints on CI (#7561)* Configure Rust lints at the workspace levelThis commit adds necessary configuration knobs to have lints configuredat the workspace level in Wasmtime rather than the crate level. Thisuses a feature of Cargo first released with 1.74.0 (last week) of the`[workspace.lints]` table. This should help create a more consistent setof lints applied across all crates in our workspace in addition topossibly running select clippy lints on CI as well.* Move `unused_extern_crates` to the workspace levelThis commit configures a `deny` lint level for the`unused_extern_crates` lint to the workspace level rather than theprevious configuration at the individual crate level.* Move `trivial_numeric_casts` to workspace level* Change workspace lint levels to `warn`CI will ensure that these don't get checked into the codebase andotherwise provide fewer speed bumps for in-process development.* Move `unstable_features` lint to workspace level* Move `unused_import_braces` lint to workspace level* Start running Clippy on CIThis commit configures our CI to run `cargo clippy --workspace` for allmerged PRs. Historically this hasn't been all the feasible due to theamount of configuration required to control the number of warnings onCI, but with Cargo's new `[lint]` table it's possible to have aone-liner to silence all lints from Clippy by default. This commit bydefault sets the `all` lint in Clippy to `allow` to by-default disablewarnings from Clippy. The goal of this PR is to enable selective accessto Clippy lints for Wasmtime on CI.* Selectively enable `clippy::cast_sign_loss`This would have fixed #7558 so try to head off future issues with thatby warning against this situation in a few crates. This lint is stillquite noisy though for Cranelift for example so it's not worthwhile atthis time to enable it for the whole workspace.* Fix CI errorprtest:full List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

62fdafa1 - Remove clippy configuration from repo and crates (#6927)

Tue, 29 Aug 2023 21:07:27 +0000

Remove clippy configuration from repo and crates (#6927)Wasmtime's CI does not run clippy so there's no enforcement of thisconfiguration. Additionally the configuration per-crate is not uniformlyapplied across all of the Wasmtime workspace and is only on somehistorical crates. Because we don't run clippy in CI this commit removesall of the clippy annotations for allow/warn/deny from the source. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

8eccc63c - Fix tests in `--release` mode (#6308)

Sat, 29 Apr 2023 04:37:10 +0000

Fix tests in `--release` mode (#6308)Add `#[cfg]` annotations to some tests which rely on `debug_assert!` forpanics. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

00f357c0 - Cranelift: support 14-bit Type index with some bitpacking. (#4269)

Tue, 05 Jul 2022 21:51:02 +0000

Cranelift: support 14-bit Type index with some bitpacking. (#4269)* Cranelift: make `ir::Type` a `u16`. * Cranelift: pack ValueData back into 64 bits. After extending `Type` to a `u16`, `ValueData` became 12 bytes rather than 8. This packs it back down to 8 bytes (64 bits) by stealing two bits from the `Type` for the enum discriminant (leaving 14 bits for the type itself). Performance comparison (3-way between original (`ty-u8`), 16-bit `Type` (`ty-u16`), and this PR (`ty-packed`)): ``` ~/work/sightglass% target/release/sightglass-cli benchmark \ -e ~/ty-u8.so -e ~/ty-u16.so -e ~/ty-packed.so \ --iterations-per-process 10 --processes 2 \ benchmarks-next/spidermonkey/benchmark.wasm compilation benchmarks-next/spidermonkey/benchmark.wasm cycles [20654406874 21749213920.50 22958520306] /home/cfallin/ty-packed.so [22227738316 22584704883.90 22916433748] /home/cfallin/ty-u16.so [20659150490 21598675968.60 22588108428] /home/cfallin/ty-u8.so nanoseconds [5435333269 5723139427.25 6041072883] /home/cfallin/ty-packed.so [5848788229 5942729637.85 6030030341] /home/cfallin/ty-u16.so [5436002390 5683248226.10 5943626225] /home/cfallin/ty-u8.so ``` So, when compiling SpiderMonkey.wasm, making `Type` 16 bits regresses performance by 4.5% (5.683s -> 5.723s), while this PR gets 14 bits for a 1.0% cost (5.683s -> 5.723s). That's still not great, and we can likely do better, but it's a start. * Fix test failure: entities to/from u32 via `{from,to}_bits`, not `{from,to}_u32`. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

1b9ff6b1 - �� rust fmt

Fri, 16 Jul 2021 20:41:44 +0000

�� rust fmt List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

87726882 - ✅ add test cases for new `entity_impl!` form

Fri, 16 Jul 2021 18:21:31 +0000

✅ add test cases for new `entity_impl!` form List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

2e8f7bac - �� provide a new form of `entity_impl!`

Fri, 16 Jul 2021 15:35:29 +0000

�� provide a new form of `entity_impl!`N.B. There is likely still some light refactoring to do, so that we arenot duplicating so much code. We should also additionally introduce sometest coverage. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

d3277c00 - �� add simple entity tests

Fri, 16 Jul 2021 15:37:18 +0000

�� add simple entity tests List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

c77ea0c5 - Add some more `#[inline]` annotations for trivial functions (#2817)

Thu, 08 Apr 2021 17:23:54 +0000

Add some more `#[inline]` annotations for trivial functions (#2817)Looking at some profiles these or their related functions were all showing up, so this commit adds `#[inline]` to allow cross-crate inlining by default. List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

c9e8889d - Update clippy annotation to use latest version (#2375)

Mon, 09 Nov 2020 15:24:59 +0000

Update clippy annotation to use latest version (#2375) List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs

6849dc40 - Fix typo in generated documentation for `entity!` (#2176)

Mon, 31 Aug 2020 08:40:24 +0000

Fix typo in generated documentation for `entity!` (#2176)* entity: Fix typo in generated documentation The same function documentation was used for `from_u32()` and `as_u32()` while their behaviour is different List of files: /wasmtime-44.0.1/cranelift/entity/src/lib.rs