Changes in codegen_settings.rs

37553b2c - chore: remove repetitive word in comment (#11887)

Mon, 20 Oct 2025 14:48:58 +0000

chore: remove repetitive word in comment (#11887)Signed-off-by: withtimezone List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

ba4e22bc - Make it easier to reuse fuzzing configuration on the CLI (#10123)

Mon, 27 Jan 2025 21:34:55 +0000

Make it easier to reuse fuzzing configuration on the CLI (#10123)* Make it easier to reuse fuzzing configuration on the CLIDuring fuzzing we emit a debug log of configured options to assist withreproducing fuzz test cases outside of the fuzzing harness. Mappingoptions the fuzzer is using though to CLI flags, for example, is a bitof an art though and not obvious. Just today we've got a fuzz bug and Icouldn't figure out how to reproduce on the CLI and it turns out theissue was that I was forgetting a flag that was being configured inresponse to another flag. I got a bit fed up with constantly trying tomap one to the other, so I've decided to fix things.This commit adds a `Display for CommonOptions` implementation to the`wasmtime-cli-flags` crate. This is built on the same macro-constructioninfrastructure of all our flags making it a relatively low one-time-costto implement this. Each option value now implements not only parsing butprinting as well.Next the `wasmtime-fuzzing` crate was updated to create a`CommonOptions` first which is then in turn used to create a`wasmtime::Config`. This provides a layer to insert a log statement withto emit all configuration options in a form that can be easilycopy/pasted to the CLI to reproduce.Overall after doing this I was able to quickly reproduce the bug inquestion (yay!). The CLI flag logging is pretty verbose right now sincethe fuzzing infrastructure sets many settings redundantly to theirdefaults, but reducing flags to a minimum is expected to be relativelyeasy compared to otherwise trying to extract the options.* Fix build and dependencies from wasmtime-fuzzing* Always provide `wasmtime::MpkEnabled`It's an otherwise very small `enum` which makes it easier toconditionally compile `wasmtime-cli-flags`* Frob some crate features some more* Fix specification of `wasmtime_linkopt_force_jump_veneer` option List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

4d75ebd1 - Fuzzing: Keep AVX flags enabled for Winch (#10052)

Tue, 21 Jan 2025 21:19:11 +0000

Fuzzing: Keep AVX flags enabled for Winch (#10052)* Fuzzing: Keep AVX flags enabled for Winch* Check that SIMD is enabled* Inspect flags in wast oracle* Add log statement List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.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/crates/fuzzing/src/generators/codegen_settings.rs

3036e795 - Add I128 atomic support to the `x64` backend (#9459)

Mon, 14 Oct 2024 21:33:08 +0000

Add I128 atomic support to the `x64` backend (#9459)* Add I128 atomic support to the `x64` backend* fix typo in cranelift/codegen/src/isa/x64/inst/emit.rs---------Co-authored-by: Nick Fitzgerald List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

3f5c21bf - Add initial f16 and f128 support to the aarch64 backend (#9076)

Fri, 16 Aug 2024 17:34:13 +0000

Add initial f16 and f128 support to the aarch64 backend (#9076) List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

0c980788 - x64: Lower SIMD requirement to SSE2 (#6625)

Thu, 22 Jun 2023 17:23:57 +0000

x64: Lower SIMD requirement to SSE2 (#6625)All instructions in Cranelift now have lowerings for SSE2 as a baseline,even if they're not exactly the speediest things in the world. Thisenables lowering the baseline required for the SIMD proposal forWebAssembly to SSE2, the base features set of x86_64. Lots of tests wereupdated here to remove explicit `has_foo=false` annotations as they nolonger have any effect.Additionally fuzzing has been updated to enable disabling `sse3` and`ssse3` which will help stress-test all previously-added lowerings. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

8fb41ca4 - x64: Don't require SSE4.1 for `enable_simd` (#6489)

Thu, 01 Jun 2023 15:20:31 +0000

x64: Don't require SSE4.1 for `enable_simd` (#6489)This commit removes the SSE4.1 requirement for the `enable_simd` CLIFfeature. This means that the new baseline required is SSSE3 for theWebAssembly SIMD proposal. Many existing tests for codegen were allupdated to explicitly enable `has_sse41` and runtests were updated totest with and without SSE 4.1.Wasmtime's fuzzing is additionally updated to flip the SSE4.1 feature toenable fuzz-testing this. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

2d25db04 - x64: Lower SIMD requirement to SSE4.1 from SSE4.2 (#6206)

Fri, 14 Apr 2023 17:24:43 +0000

x64: Lower SIMD requirement to SSE4.1 from SSE4.2 (#6206)Cranelift only has one instruction SIMD which depends on SSE4.2 so thiscommit adds a lowering rule for `pcmpgtq` which doesn't use SSE4.2 andenables lowering the baseline requirement for SIMD support from SSE4.2to SSE4.1.The `has_sse42` setting is no longer enabled by default for Cranelift.Additionally `enable_simd` no longer requires `has_sse42` on x64.Finally the fuzz-generator for Wasmtime codegen settings now enablesflipping the `has_sse42` setting instead of unconditionally setting itto `true`.The specific lowering for `pcmpgtq` is copied from LLVM's lowering ofthis instruction. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

9b896d2a - Resolve libcall relocations for older CPUs (#5567)

Wed, 18 Jan 2023 15:04:10 +0000

Resolve libcall relocations for older CPUs (#5567)* Resolve libcall relocations for older CPUs Long ago Wasmtime used to have logic for resolving relocations post-compilation for libcalls which I ended up removing during refactorings last year. As #5563 points out, however, it's possible to get Wasmtime to panic by disabling SSE features which forces Cranelift to use libcalls for some floating-point operations instead. Note that this also requires disabling SIMD because SIMD support has a baseline of SSE 4.2. This commit pulls back the old implementations of various libcalls and reimplements logic necessary to have them work on CPUs without SSE 4.2 Closes #5563 * Fix log message in `wast` support * Fix offset listed in relocations Be sure to factor in the offset of the function itself * Review comments List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

d8b29089 - Initial forward-edge CFI implementation (#3693)

Thu, 08 Sep 2022 14:35:58 +0000

Initial forward-edge CFI implementation (#3693)* Initial forward-edge CFI implementation Give the user the option to start all basic blocks that are targets of indirect branches with the BTI instruction introduced by the Branch Target Identification extension to the Arm instruction set architecture. Copyright (c) 2022, Arm Limited. * Refactor `from_artifacts` to avoid second `make_executable` (#1) This involves "parsing" twice but this is parsing just the header of an ELF file so it's not a very intensive operation and should be ok to do twice. * Address the code review feedback Copyright (c) 2022, Arm Limited. Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

1481721c - Enable back-edge CFI by default on macOS (#4720)

Wed, 17 Aug 2022 20:06:20 +0000

Enable back-edge CFI by default on macOS (#4720)Also, adjust the tests that are executed on that platform. Finally, fix a bug with obtaining backtraces when back-edge CFI is enabled. Copyright (c) 2022, Arm Limited. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

02c3b47d - x64: Implement SIMD `fma` (#4474)

Mon, 25 Jul 2022 22:01:02 +0000

x64: Implement SIMD `fma` (#4474)* x64: Add VEX Instruction Encoder This uses a similar builder pattern to the EVEX Encoder. Does not yet support memory accesses. * x64: Add FMA Flag * x64: Implement SIMD `fma` * x64: Use 4 register Vex Inst * x64: Reorder VEX pretty print args List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs

c227063f - fuzz: refactor fuzz generators (#4404)

Thu, 07 Jul 2022 18:44:27 +0000

fuzz: refactor fuzz generators (#4404)Previously, much of the logic for generating the various objects needed for fuzzing was concentrated primarily in `generators.rs`. In trying to piece together what code does what, the size of the file and the light documentation make it hard to discern what each part does. Since several generator structures had been split out as separate modules in the `generators/` directory, this change takes that refactoring further by moving the structures in `generators.rs` to their own modules. No logic changes were made, only the addition of documentation in a few places. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/codegen_settings.rs