merge revision(s) efcdf68e6443ab70fbff1703b9dabbfc5090df31,5e26619660f20272a53c7f839dde36cce034bb35: [Backport #17539]

	Guard callinfo

	Callinfo was being written in to an array and the GC would not see the
	reference on the stack.  `new_insn_send` creates a new callinfo object,
	then it calls `new_insn_core`.  `new_insn_core` allocates a new INSN
	linked list item, which can end up calling `xmalloc` which will trigger
	a GC:

	  https://github.com/ruby/ruby/blob/70cd351c7c71c48ee18d7c01e851a89614086f8f/compile.c#L968-L969

	Since the callinfo object isn't on the stack, the GC won't see it, and
	it can get collected.  This patch just refactors `new_insn_send` to keep
	the object on the stack

	Co-authored-by: John Hawthorn <john@hawthorn.email>
	---
	 compile.c            |  7 +++++--
	 test/ruby/test_gc.rb | 10 ++++++++++
	 2 files changed, 15 insertions(+), 2 deletions(-)

	Fix WB for callinfo

	The WB for callinfo needs to be executed *after* the reference is
	written.  Otherwise we get a WB miss.
	---
	 compile.c | 1 +
	 1 file changed, 1 insertion(+)

0 files changed, 0 insertions, 0 deletions