Already part of D63152

Thanks for the reviews. I'm changing the new test to take a mir obtained just before shrink-wrap pass and validating just that one pass.

Hi @thegameg,
My initial thoughts on how to optimize this was to use alias analysis to check that load and stores for sure do not alias with the stack of the current function. It seems that the current api accepts two memory operands, and then turns them into memory regions. I don't know if it possible, as we might not know the sp value it self, but my idea was to create a function that accepts a memory access and a memory region, which would be set to [SP, SP + stackSize].
In pr42136, @eli.friedman also mentioned that might be quite simple to prove that a load accesses a global variable, as well possible to prove that the address of some particular stack objects doesn't escape (also pointed by @chill) .

• - Added specific shrink wrapping test for pr37472

Fixed.

[ARM][FIX] Ran out of registers due tail recursion

Moved conversion to the existing folding loop

Removed duplicated %s in test file.

Fixes requested

• removed old apcs

Added new conversions, tests, and different float-abi

Tests updated

Fixed duplicates

Waiting for the outcome of D60691.

• Added big-endian tests

Moved tests to D60720

• Added tests

Sorry, I don't believe I ever touched these files before.

• Used clang-format-diff

Moved to agressiveInstCombine.

Ping

Ping

Added transformation for comparing.

Moved tests to existing vector test file.

Ping.
I know the usual time is a week, but for such a small bug-fix I don't believe much more people would care.

In D60259#1454767, @LukeGeeson wrote:

Would it be possible to see the surrounding tests for fp16_intrinic_scalar_2op? It'd be good to double check formatting

Attended requests.