Skip to content

Conversation

@Amanieu
Copy link

@Amanieu Amanieu commented Jul 10, 2025

@cfallin
Copy link
Member

cfallin commented Jul 11, 2025

To clarify from the Cranelift side (as discussed in our most recent weekly meeting): we are still evaluating whether we will add regalloc3 as a register allocator backend, with the final decision depending on code review and discussions around maintenance going forward. So it's great to get this step's discussion started now, but I suspect its finalization may want to wait on Cranelift's process as a dependency (though of course that's ultimately up to both the TSC and you!).

@tschneidereit
Copy link
Member

@Amanieu, we discussed this proposal in today's TSC meeting. It seems like the Cranelift team's decision against integrating regalloc3 into regalloc2/Cranelift for the time being might impact the application. In light of that, we wanted to check with you whether you're still interested in contributing the project, and whether the answers in the application all still hold as before. If you still are interested, we're happy to do a full review of the application (amended to whatever degree necessary.)

@Amanieu
Copy link
Author

Amanieu commented Jul 25, 2025

Considering the Cranelift team's decision, I don't think it makes sense to move regalloc3 to the Bytecode Alliance at this time.

@Amanieu Amanieu closed this Jul 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants