finagolfin

Any plans to put out a 5.3 build? I just put out a release for Android ARMv7, termux/termux-packages#5843, and you'll be happy to know it didn't require much patching (though...

>Do the macros still partially work or are they completely broken (hope not)? I don't know to what extent, but I assume completely since basic constants like `#define EXIT_SUCCESS 0`...

> Can confirm it works with 5.1.5 Good to know, that means diffing that Swift ClangImporter source to 5.3 might turn up something, assuming you hit this bug with 5.3...

Btw, the static stdlib patch I used is mostly apple/swift@e8fe229 combined with a one-line fix added later, apple/swift@da65420, and of course a couple Android tweaks.

Any luck with that build or is it still compiling? 😉 I tracked that Macro ClangImporter bug to when it's loading C modules in `loadModuleClang()`, both [this call to `CompilerInstance::loadModule()`](https://github.com/apple/swift/blob/release/5.3/lib/ClangImporter/ClangImporter.cpp#L1728)...

>both armv7 and armv6 still fail with the same error Meaning you cannot import Macro constants too? Does hello world work? That is fine on Android ARMv7 and I'm also...

Is that `alignas` really necessary? Does it build if you remove it?

Here's the list of compiler flags used to compile `lib/AST/ImportCache.cpp`, which you can get by going into the Swift build directory and running `ninja -t commands | ag AST/ImportCache.cpp`: is...

Hmm, that is weird: are you compiling natively or cross-compiling? I'm doing the latter and I use the Android NDK clang to cross-compile the Swift compiler, so our different results...

I just looked into it and the native build uses the host clang to build the Swift compiler, ie the same host clang used to compile the LLVM toolchain source...