Vaivaswatha N

This is ready for review now. I'm going open new Issue(s) for further related improvements.

> @vaivaswatha seems like one of the tests might be flaky ... > > ``` > Failing tests: > should_pass/unit_tests/regalloc_spill ... failed > ``` I updated `Forc.lock` for that test...

The error reported here should be solved by #4628. However just as with #4511 and #4625 , after the fix, I'm seeing ``` error: Internal compiler error: The allocator cannot...

On second thought, I'll leave the issue open and close it after it all works, just to be sure.

When I worked on #4592, without `local_copy_prop_prememcpy`, the test `u256_ops_test` wouldn't compile. That was because, the new optimization inserted instructions at the beginning of the block, when the use was...

@IGI-111 I experiemented with removing `local_copy_prop_prememcpy` and here the numbers. My suggestion is to still go ahead removing that optimization pass (because it is badly written, at that time for...

> We can have another tracker issue to catch what patterns of memory copy propagation we're missing and try to incorporate that into the current pass (i.e., the one added...

> Perhaps it would make sense to run benchmarks on the projects from https://github.com/FuelLabs/sway-applications, instead of the Sway test suite? Ah yes. Let me do that.

> Perhaps it would make sense to run benchmarks on the projects from https://github.com/FuelLabs/sway-applications, instead of the Sway test suite? I gave this a try, but I have trouble building...

@SwayStar123 this should be fixed with #4628 . Once that is merged, please verify.