Stream: git-wasmtime

Topic: wasmtime / PR #13250 Refactor how inlining is configured ...

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton opened PR #13250 from alexcrichton:refactor-inlining to bytecodealliance:main:

Fold the inlining boolean and the inlining_intra_module options into a single Inlining enum option. This option encompasses both and has an additional mode which is "only intrinsics" where inter-module and intra-module calls are never inlined, but intrinsics for Wasmtime are allowed to be inlined. This is inspired from discussion on #13214 and after some performance work and/or confirmations the expectation is to turn the default inlining mode to Inlining::Intrinsics.

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton requested fitzgen for a review on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton requested wasmtime-core-reviewers for a review on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton requested wasmtime-compiler-reviewers for a review on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 20:46):

alexcrichton requested wasmtime-default-reviewers for a review on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 20:47):

alexcrichton commented on PR #13250:

A few points of note here:

• This PR is not seeking to change the default of "inlining is off"
• This PR changes the meaning of -Cinlining to "inline everything you can" as opposed to the previous WhenUsingGc option.

Wasmtime GitHub notifications bot (May 01 2026 at 21:10):

alexcrichton updated PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 23:59):

github-actions[bot] added the label wasmtime:api on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 23:59):

github-actions[bot] added the label fuzzing on PR #13250.

Wasmtime GitHub notifications bot (May 01 2026 at 23:59):

github-actions[bot] added the label wasmtime:config on PR #13250.

Wasmtime GitHub notifications bot (May 02 2026 at 00:00):

github-actions[bot] commented on PR #13250:

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing", "wasmtime:api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

• fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (May 02 2026 at 01:15):

github-actions[bot] commented on PR #13250:

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

• [ ] If you added a new Config method, you wrote extensive documentation for
  it.

  <details>

  Our documentation should be of the following form:

  ```text
  Short, simple summary sentence.

  More details. These details can be multiple paragraphs. There should be
  information about not just the method, but its parameters and results as
  well.

  Is this method fallible? If so, when can it return an error?

  Can this method panic? If so, when does it panic?

  Example

  Optional example here.
  ```

  </details>

• [ ] If you added a new Config method, or modified an existing one, you
  ensured that this configuration is exercised by the fuzz targets.

  <details>

  For example, if you expose a new strategy for allocating the next instance
  slot inside the pooling allocator, you should ensure that at least one of our
  fuzz targets exercises that new strategy.

  Often, all that is required of you is to ensure that there is a knob for this
  configuration option in [wasmtime_fuzzing::Config][fuzzing-config] (or one
  of its nested structs).

  Rarely, this may require authoring a new fuzz target to specifically test this
  configuration. See [our docs on fuzzing][fuzzing-docs] for more details.

  </details>

• [ ] If you are enabling a configuration option by default, make sure that it
  has been fuzzed for at least two weeks before turning it on by default.

[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html

---

<details>

To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.

To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.

Learn more.

</details>

Last updated: May 03 2026 at 22:13 UTC