Stream: git-wasmtime

Topic: wasmtime / PR #11714 asm: add `num_registers_available()`

Wasmtime GitHub notifications bot (Sep 18 2025 at 23:30):

abrown requested wasmtime-compiler-reviewers for a review on PR #11714.

Wasmtime GitHub notifications bot (Sep 18 2025 at 23:30):

abrown opened PR #11714 from abrown:apx-num-regs-available to bytecodealliance:main:

This change adds a way to inspect how many registers an instruction can address. We assume for now that legacy instructions can always emit the REX prefix and thus access 16 registers; thus, the only encoding that allows access to 32 registers is EVEX.

This also refactors some of the top-level generation logic to be less verbose.

<!--
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 (Sep 18 2025 at 23:30):

abrown requested fitzgen for a review on PR #11714.

Wasmtime GitHub notifications bot (Sep 23 2025 at 16:55):

fitzgen submitted PR review.

Wasmtime GitHub notifications bot (Oct 03 2025 at 22:53):

rahulchaphalkar commented on PR #11714:

I was looking to see why something failed in the merge queue, and can see Successful test and build passing, but then Report failure on cancellation being triggered.
Digging through logs, i see the following 2 jobs reported a cancellation - Test Linux s390x and Test on armv7...
I don't have much context on why these jobs would be cancelled, but I do see a recent change https://github.com/bytecodealliance/wasmtime/commit/2f77c2b993217f8d94e8e3e0bddea328fca95835 which changes this ci logic, worth re adding to the merge queue?

Wasmtime GitHub notifications bot (Oct 04 2025 at 00:10):

alexcrichton merged PR #11714.

Last updated: Jan 09 2026 at 13:15 UTC