Skip to content

wasmtime: change the name of the regalloc2 fuzzer - #14053

Merged
DavidKorczynski merged 1 commit into
google:masterfrom
abrown:regalloc2-target-rename
Sep 24, 2025
Merged

DavidKorczynski merged 1 commit into
google:masterfrom
abrown:regalloc2-target-rename

Conversation

@abrown

@abrown abrown commented Sep 23, 2025

Copy link
Copy Markdown
Contributor

This change coordinates a name change to regalloc2's fuzz targets introduced in #244. The ion_checker target is now simply named ion.

@abrown

abrown commented Sep 23, 2025 •

Copy link
Copy Markdown
Contributor Author

This should not be merged before bytecodealliance/regalloc2#244.

EDIT: this should now be fine to merge.

@github-actions

Copy link
Copy Markdown

abrown has previously contributed to projects/wasmtime. The previous PR was #6205

@abrown
abrown marked this pull request as ready for review September 23, 2025 21:42
This change coordinates a name change to `regalloc2`'s fuzz targets
introduced in [google#244]. The `ion_checker` target is now simply named
`ion`.

[google#244]: bytecodealliance/regalloc2#244
@abrown
abrown force-pushed the regalloc2-target-rename branch from a368764 to 0f3e403 Compare September 24, 2025 04:23
@DavidKorczynski
DavidKorczynski merged commit 0d62e34 into google:master Sep 24, 2025
15 checks passed
@abrown
abrown deleted the regalloc2-target-rename branch September 24, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants