This is a tracking issue collecting all of our ideas for improving Wasm GC performance and potential optimizations we could implement.

• Speed up getting and setting funcref elements/fields in GC objects #9347
• Avoid locks for subtyping checks in Wasm GC #9352
• Reuse linear memories, and our code to emit their bound checks, for Wasm GC heaps #9350
• Escape analysis for Wasm GC #9349
• Type-based alias analysis for Wasm GC #9348
• cranelift/egraphs: allow simplifying trapping arithmetic #5908
• Const fold through uadd_overflow_trap/trap{z,nz} insts that show up frequently in GC heap accesses. Depends on cranelift/egraphs: allow simplifying trapping arithmetic #5908
• Also add a mid-end rule like (uadd_overflow_trap (uextend x) (uextend y)) ==> (iadd (uextend x) (uextend y)). Depends on cranelift/egraphs: allow simplifying trapping arithmetic #5908
• Use bulk memcpy-style APIs to implement array.copy when possible and do GC barriers inline when not possible
• Expose type registry's supertypes arrays to Wasm, so it can do the O(1) subtype checks inline
• Propagate trapz backwards from ref.cast into the branch-y instance-of check that it emits. Similar for the jumps inside a br_on_cast[_fail]'s instance-of check. See Implement the ref.cast Wasm GC instruction #9437 (comment) for details. Alternatively, clean this stuff up in the mid-end: cranelift/egraphs: Optimize instructions without results #6106
• Speed up call_indirect in the face of subtyping. Much of this can be addressed by letting Wasm to the O(1) subtype checks inline, but it is still additional work to be done on every call_indirect vs MVP wasm. We should investigate inline caches and such again.