Stream: git-wasmtime

Topic: wasmtime / PR #10618 remove compiler cfg on configured ta...

Wasmtime GitHub notifications bot (Apr 20 2025 at 11:05):

isoadam requested fitzgen for a review on PR #10618.

Wasmtime GitHub notifications bot (Apr 20 2025 at 11:05):

isoadam requested wasmtime-core-reviewers for a review on PR #10618.

Wasmtime GitHub notifications bot (Apr 20 2025 at 11:05):

isoadam opened PR #10618 from isoadam:configured-target to bytecodealliance:main:

<!--
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
-->

New changes from stale PR: https://github.com/bytecodealliance/wasmtime/pull/10197

Pulley can now be used without a compiler, but this line prevents the configured target (pulley64, etc) from actually being used.

Wasmtime GitHub notifications bot (Apr 20 2025 at 12:54):

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

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>

Wasmtime GitHub notifications bot (Apr 21 2025 at 14:37):

alexcrichton submitted PR review:

Thanks!

Wasmtime GitHub notifications bot (Apr 21 2025 at 14:59):

alexcrichton merged PR #10618.

Last updated: Dec 06 2025 at 07:03 UTC