Regression on number of allocations in GC micro-benchmark about julia HOT 3 CLOSED

1c25d93 is the cause of 2M alloc -> 4M alloc at least (but it doesn't seem to have that much of a perf impact)

~/julia$ manyjulias $(git rev-parse HEAD) -t8 testit.jl 
Extracted 'julia-1_12_0-DEV_0:1c25d93ca8ab3f5b0cad627d76705fb7025429a3'
  9.980486 seconds (3.81 M allocations: 29.817 GiB, 31.02% gc time, 51.06% compilation time: 74% of which was recompilation)

~/julia$ manyjulias $(git rev-parse HEAD)~1 -t8 testit.jl 
Extracted 'julia-1_12_0-DEV_0:c0a93f8c3ef20fe9f892e1a728409c60599657cc'
  9.533646 seconds (1.99 M allocations: 29.789 GiB, 30.31% gc time, 48.24% compilation time)

It's a perhaps bit surprising that the one with the slower compilation has recompilation while the previous one do not.

cc @Keno

from julia.

While it is unfortunate with a perf regression I don't think it really warrants being on the milestone.

from julia.

the regression still exists on 1.11, but it looks like it's resolved on master, so this would only appear specifically in the 1.11.x releases (unless it re-regresses)

from julia.