In D63152#1628975, @wuzish wrote:

Is there any fix patch proposed to track/fix the regression? @dnsampaio

Just seen that this breaks clang/test/Sema/struct-packed-align.c, working on it.

I have tested this in our MacOS and linux environments. @thakis @thegameg @phosek, would it be possible for you to check if this works for you?

Fix test

Hi, first thanks for those that looked into this and sorry for the delay.
We have investigated the errors and seems that the test was, first in the wrong folder, inside CodeGen where it should be in CodeGenCXX and we should use clang_cc1.

True. Thx again.

• Joined assignments for default alignments and neon_vector alignment
• Added missing align 8 test

• Joined assignments for default alignments and neon_vector alignment

Set android-abi default to 128. Added tests for android and not-android.

• Set androideabi alignment to 128 bits

Was fixed just after if the include <atomic>

I am getting this error with gcc 8.2

/work/bf/LLVM/local/src/lib/Support/PrettyStackTrace.cpp:57:39: error: variable ‘volatile std::atomic<unsigned int> GlobalSigInfoGenerationCounter’ has initializer but incomplete type
 static volatile std::atomic<unsigned> GlobalSigInfoGenerationCounter =
                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

• Fix previously existing tests

• Added tests

In D64210#1570515, @LukeCheeseman wrote:

Are there some changes/addition to tests attached to this?

Perhaps this makes it clearer:
https://rise4fun.com/Alive/4TLv

Hi @lebedev.ri,
Nice you looked this one as I am not quite sure what to do about it. Any suggestions?

Fixed inline requests

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