In D128874#3621115, @wallace wrote:

thanks!

FYI: failure looks like the following:

@sstwcw @HazardyKnusperkeks : this change introduced a regression in one of the clang format unit tests. I fixed it in the revision below. Could anyone please take a look / approve this revision to unblock Windows debug builds? Thanks!

In D121102#3366800, @csigg wrote:

In D121102#3366204, @kevcadieux wrote:

Hello @csigg, there seems to be another use of the deprecated parseSourceString function in mlir/lib/CAPI/IR/IR.cpp that is causing a deprecated error in our builds. Would you mind please updating that use as well? Thanks!

Done.

Does that mean that we are not supposed to mark things deprecated?
Or would it make sense to only treat deprecations as warnings in your build?

Hello @csigg, there seems to be another use of the deprecated parseSourceString function in mlir/lib/CAPI/IR/IR.cpp that is causing a deprecated error in our builds. Would you mind please updating that use as well? Thanks!

In D113809#3147527, @smeenai wrote:

https://github.com/llvm/llvm-project/commit/2f5d6a0ea51b should fix the assertion. Sorry for the breakage here.

We are also seeing this in our internal Windows builds. As can be seen below, the size difference in debug is due to the std::vector<lld::macho::Reloc> member, which is actually due to the _Vector_val internal vector member that uses a different base class in debug mode (std::_Container_base12 instead of std::_Container_base0). Could we simply turn off this static assert for debug builds (e.g. with #ifdef NDEBUG)?

In D113242#3136329, @llvm-commits wrote:

Sure—please let me know the email address and author name to I use for attribution!

In D113242#3129079, @dexonsmith wrote:

LGTM.

Rebasing.

In D113242#3112628, @Meinersbur wrote:

The Polly failure was fixed here: https://github.com/llvm/llvm-project/commit/7f627596977624730f9298a1b69883af1555765e

There are build failures due to a failed Polly test

test/ScopInliner/simple-inline-loop.ll